In bug 704258 we have the following atom in the list: dev-cpp/glog-0.4.0 arm arm64 ppc ppc64 sparc However dev-cpp/glog-0.4.0 needs sys-libs/libunwind which is not available on sparc: Keywords for sys-libs/libunwind: | | u | | a a a p s r | n | | l m r i p h m s p i m | e u s | r | p d a m a p c x p 6 3 a s i | a s l | e | h 6 r 6 6 p 6 8 p 8 9 s r c p | p e o | p | a 4 m 4 4 c 4 6 a k 0 h c v s | i d t | o ---------+-------------------------------+---------+------- 1.2.1-r3 | o + + + + + + + + o o o - o ~ | 6 o 7 | gentoo So I'd expect that sparc is not cc'ed in bugs like this.. Thanks
stable-bot doesn't pass `-y e` to repoman - all sparc profiles are in exp
Given the all-or-nothing state of the 'sanity-check+' flag and the poor state of deptree consistency across various exp arches, the bot only checks arches with stable and dev (since bug #648554) profiles. I'm happy to consider behaviour changes, but given how few people seem to care about stabilisation of exp arches, I'm unsure if it will be worth the effort.
The point for me is: if I'm using it, I expect to have a valid list in "package list" field, that is the reason because the stable-bot was born
Perhaps I wasn't clear. This was designed from day one to support only architectures with stable profiles. sparc no longer has any stable profiles so there is no expectation of a consistent depgraph, and stable-bot does not support it. The arches had their stable supported status removed for a reason. If we require arches with unstable profiles to also have a consistent depgraph before flagging sanity-check+, the usefulness of the flag is essentially reduced to zero - the entire stabilisation request is blocked until an arch with an already-broken depgraph (and no requirement to do anything about it) fixes everything. If sparc wants stable-bot support, I can see two options: * sparc profiles are marked as stable again necessitating a consistent depgraph * refactoring the stable-bot process to have per-arch flags - eg. sanity-check-amd64+, sanity-check-sparc-, sanity-check-x86+ I am happy to do whatever I can to support either of these options, but I do not have the capacity to drive either of them right now.
stable-bot is now dead - please use nattka instead.
