3.3.23 was bumped as SLOT=0 without explanation and without blocking SLOT=3.12, however two revdeps depend on SLOT=3.12 blocking stabilisation/cleanup. Why is that so? > commit be40870874711d398762b80ed81c2f3dd7242c58 > Author: Patrick Lauer <patrick@gentoo.org> > Date: Mon Mar 1 15:42:35 2021 +0000 > > sys-fabric/opensm: Bump > > Package-Manager: Portage-3.0.16, Repoman-3.0.2 $ eshowkw opensm Keywords for sys-fabric/opensm: | | u | | a a p s a r | n | | m r h p p l i i m m s | e u s | r | d a m p p c a x p a s 6 i 3 | a s l | e | 6 r 6 p p 6 r 8 h 6 c 8 p 9 | p e o | p | 4 m 4 a c 4 c 6 a 4 v k s 0 | i d t | o ----------+-----------------------------+----------+------- 3.3.17-r1 | + o o o o o o ~ o o o o o o | 5 o 3.12 | gentoo ----------+-----------------------------+----------+------- 3.3.23-r1 | ~ o o o o o o ~ o o o o o o | 7 o 0 | gentoo > sys-fabric/infiniband-diags:3.12 sys-fabric/opensm:${SLOT} > sys-fabric/ofed-3.12_rc1:3.12 sys-fabric/opensm:${SLOT}
ping
no answer is good answer I guess.
amd64 done
x86 done all arches done
Re-opening for cleanup. Waiting for maintainer timeout again I guess?
This will be resolved by masking 3.3.17-r1 along with other packages in bug 830999
Last-rited in a8d67eb0ac4ef3dfb726aad6cf527b5c0d4ed03f
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=763ebb8e02ca1b79c9df0baafbdf5aa1b9d9e70d commit 763ebb8e02ca1b79c9df0baafbdf5aa1b9d9e70d Author: Jakov Smolić <jsmolic@gentoo.org> AuthorDate: 2022-02-15 09:07:58 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2022-02-15 09:22:30 +0000 sys-fabric/opensm: drop 3.3.17-r1 Closes: https://bugs.gentoo.org/783747 Closes: https://bugs.gentoo.org/806290 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> sys-fabric/opensm/Manifest | 1 - sys-fabric/opensm/opensm-3.3.17-r1.ebuild | 60 ------------------------------- 2 files changed, 61 deletions(-)
