media-gfx/imagemagick-6.2.9.5: vulnerable via glsa(200611-19) ( ver < 6.3.0.5 ), affects ('alpha', 'amd64', 'arm', 'hppa', 'ia64', 'mips', 'ppc', 'ppc-macos', 'ppc64', 'sh', 'sparc', 'x86', 'x86-fbsd') media-gfx/imagemagick-6.2.9.5-r1: vulnerable via glsa(200611-19) ( ver < 6.3.0.5 ), affects ('alpha', 'amd64', 'arm', 'hppa', 'ia64', 'mips', 'ppc', 'ppc-macos', 'ppc64', 'sh', 'sparc', 'x86', 'x86-fbsd') Please, remove the above once 6.3.0.5 has been stabilized on mips. Thanks. :)
Seems the standard trolls are coming out of the woodwork about this bug. I'd like to comment. Jakub clearly stated after mips was stabilized. In reality that is even not a concern at this time. If it's an unsupported security arch then said $ARCH is simply out of luck in these situations. There is no guarantees what so ever that maintainers need to bother concerning themselves with keyword dropping for a arch that is unsupported. The only way to make any reasonable guarantees what so ever is to become a supported arch. While in an ideal world it would be nice and not screw up an arch.
(In reply to comment #1) > Seems the standard trolls are coming out of the woodwork about this bug. I'd > Jakub clearly stated after mips was stabilized. In reality that is even > not a concern at this time. If it's an unsupported security arch then > said $ARCH is simply out of luck in these situations. There is no > guarantees what so ever that maintainers need to bother concerning > themselves with keyword dropping for a arch that is unsupported. Untrue. You need to read the keywording policy again. Also remember that dropping the last stable of a package like this one leads to hundreds of broken deps across the tree. Waving around the 'security' flag is no excuse for this.
(In reply to comment #2) > (In reply to comment #1) > Also remember that dropping the last stable of a package like this one leads to > hundreds of broken deps across the tree. Waving around the 'security' flag is > no excuse for this. OMG, drama queen on the sceen... Hundreds?! Exactly two: app-doc/gimp-help and media-gfx/gimp-print.
(In reply to comment #1) > Seems the standard trolls are coming out of the woodwork about this bug. I'd > like to comment. > > Jakub clearly stated after mips was stabilized. In reality that is even > not a concern at this time. If it's an unsupported security arch then > said $ARCH is simply out of luck in these situations. There is no > guarantees what so ever that maintainers need to bother concerning > themselves with keyword dropping for a arch that is unsupported. The > only way to make any reasonable guarantees what so ever is to become a > supported arch. While in an ideal world it would be nice and not screw > up an arch. > No, policy is quite clear on this. You don't remove the newest stable version on any arch and you don't remove any versions breaking dependencies. What you can do is remove keywords from archs with newer stable versions and reassign bugs for security affected versions to the team(s) that still haven't keyworded a newer version. This has been the policy forever as documented on http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=5#doc_chap7 So sekretarz did break policy in this case even though jakub stated that mips had to be stabled first.
(In reply to comment #1) > If it's an unsupported security arch then > said $ARCH is simply out of luck in these situations. There is no > guarantees what so ever that maintainers need to bother concerning > themselves with keyword dropping for a arch that is unsupported. Not even remotely true. You do not break arch keywording, regardless of justification.
Closing this bug. Move your debates to mailing list or somewhere else (like, file yourself a MIPS stabilization bug if you really wish). This is not a discussion forum and I'm not interested in taking part in this and receiving further mails in my already flooded mailbox.