Summary: | dev-java/xmlstreambuffer-0.5.20070412-r2 :! ERROR: Package stax-ex was not found! | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | pacho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge log |
Description
Toralf Förster
2015-04-06 08:49:03 UTC
This is the result of an issue I highlighted on the gentoo-dev list just the other day. I intend to add a QA check to avoid this problem in future. In this case, the version you're trying to install is ancient and the latest version, which doesn't have this problem, should really be stabilized. The problem is that the ~x86-fbsd keyword understandably hasn't been carried forward and there seems little chance of getting it added. Dropping it would break several reverse dependencies. This keyword has been a general thorn in the side for the Java team so I have just sent the BSD team an ultimatum. I await their reply. The newest version has now been stabilised for amd64 and x86. The oldest version remains until the newest can be marked stable for ppc. I will close this when that happens. (In reply to James Le Cuirot from comment #1) > This is the result of an issue I highlighted on the gentoo-dev list just the > other day. I intend to add a QA check to avoid this problem in future. In > this case, the version you're trying to install is ancient and the latest > version, which doesn't have this problem, should really be stabilized. The > problem is that the ~x86-fbsd keyword understandably hasn't been carried > forward and there seems little chance of getting it added. Dropping it would > break several reverse dependencies. This keyword has been a general thorn in > the side for the Java team so I have just sent the BSD team an ultimatum. I > await their reply. That arch is in experimental status for a long time and, then, you can break their tree for cases like this (and repoman won't complain at all) (In reply to James Le Cuirot from comment #2) > The newest version has now been stabilised for amd64 and x86. The oldest > version remains until the newest can be marked stable for ppc. I will close > this when that happens. I cannot find the relevant bug... can you point me to it for allowing me to do ppc stabilization is possible? Thanks (In reply to Pacho Ramos from comment #3) > I cannot find the relevant bug... can you point me to it for allowing me to > do ppc stabilization is possible? Thanks There isn't one because it was too soon to stabilise it at the time. I can also apply ALLARCHES policy here so I have just marked it stable now that it's been long enough but tested it again on ppc anyway with the latest icedtea 6 and 7 for good measure. |