Version | Builds | Tests | QA |
---|---|---|---|
corosync-1.4.3-r1 | |||
corosync-1.4.5 | |||
corosync-1.3.5 | |||
corosync-1.4.4 | |||
corosync-1.3.0 | |||
corosync-1.3.3-r1 | |||
corosync-2.3.1 | |||
corosync-2.3.2 |
KEYWORDS.dropped sys-cluster/corosync/corosync-2.3.1.ebuild: hppa x86-fbsd KEYWORDS.dropped sys-cluster/corosync/corosync-2.3.2.ebuild: hppa x86-fbsd repo.eapi.deprecated sys-cluster/corosync/corosync-1.3.0.ebuild: 3
StaleUnstableKeyword: version 1.3.3-r1: no change in 763 days for unstable keywords [ ~amd64, ~hppa, ~x86, ~x86-fbsd ] StaleUnstableKeyword: version 1.3.5: no change in 751 days for unstable keywords [ ~amd64, ~hppa, ~x86, ~x86-fbsd ] StaleUnstableKeyword: version 1.4.3-r1: no change in 695 days for unstable keywords [ ~amd64, ~hppa, ~x86, ~x86-fbsd ] StaleUnstableKeyword: version 1.4.4: no change in 504 days for unstable keywords [ ~amd64, ~hppa, ~x86, ~x86-fbsd ] StaleUnstableKeyword: version 1.4.5: no change in 504 days for unstable keywords [ ~amd64, ~hppa, ~x86, ~x86-fbsd ] StaleUnstableKeyword: version 2.3.1: no change in 281 days for unstable keywords [ ~amd64, ~x86 ] StaleUnstableKeyword: version 2.3.2: no change in 231 days for unstable keywords [ ~amd64, ~x86 ] DroppedKeywordWarning: version 2.3.1: keyword x86-fbsd was dropped DroppedKeywordWarning: version 2.3.1: keyword hppa was dropped UnstableOnly: for arch x86-fbsd, all versions are unstable: [ 1.3.3-r1, 1.3.5, 1.4.3-r1, 1.4.4, 1.4.5 ] RedundantVersionWarning: version 1.3.3-r1: slot(0) keywords are overshadowed by version '1.4.5, 1.4.4, 1.4.3-r1, 1.3.5' RedundantVersionWarning: version 1.3.5: slot(0) keywords are overshadowed by version '1.4.5, 1.4.4, 1.4.3-r1' RedundantVersionWarning: version 1.4.3-r1: slot(0) keywords are overshadowed by version '1.4.5, 1.4.4' RedundantVersionWarning: version 1.4.4: slot(0) keywords are overshadowed by version '1.4.5' RedundantVersionWarning: version 2.3.1: slot(0) keywords are overshadowed by version '2.3.2'
This lists all sub-slot candidates without regard to their appropriateness. Please check with the appropriate maintainer before implementing them.
Nothing to report