dev-python/PyQt-builder has only one version, which is currently not stable. Reproducible: Always
What for?
Could you clarify your question? It sounds like you're asking me what the purpose of stabilizing a package is?
Yes. Because this package makes no sense to be keyworded without anything else depending on it, so you would likely want to add a relation to another bug.
It's a build dependency for the stable (arm64) packages dev-python/PyQt5 and dev-python/PyQtWebEngine. Emerging those stable packages requires first adding dev-python/PyQt-builder to package.accept_keywords.
Is there not a repoman, or similar qa tool, that checks to ensure all stable packages depend only on stable packages?
(In reply to Michael Jones from comment #4) > It's a build dependency for the stable (arm64) packages dev-python/PyQt5 and > dev-python/PyQtWebEngine. That is not possible by definition. > $ eshowkw PyQt5 > Keywords for dev-python/PyQt5: > | | 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 > -------------+-----------------------------+-------+------- > 5.15.4-r1 | + + + o ~ ~ o + o o ~ o o o | 7 o 0 | gentoo > [I]5.15.6 | ~ ~ ~ o ~ ~ o ~ o o ~ o o o | 8 o | gentoo 5.15.6 is ~arch and depends on dev-python/PyQt-builder. 5.15.4-r1 is arch and does *not* depend on dev-python/PyQt-builder. Conclusion: dev-python/PyQt-builder is simply a new dependency and it will naturally be stabilised *together* with the first PyQt5 version stabilisation to make that necessary, whenever that will be. arm64 will be part of it since it already has a stable PyQt5 right now.
