[gentoo-user] How to request multiple keyword removals Firefox 3.6.2?

[gentoo-user] How to request multiple keyword removals Firefox 3.6.2?

[Walter Dnes]

  Given the seriousness of the latest Firefox hole, I decided that
keywording Firefox 3.6.2 ~x86 was less of a risk than continuing to run
3.5.8.  However, there were a few ~x86 ebuild dependencies on top of
~x86 ebuild dependencies.  My /etc/portage/package.keywords ended up
with the following...

=www-client/mozilla-firefox-3.6.2 ~x86
=net-libs/xulrunner-1.9.2.2-r1 ~x86
=dev-libs/nss-3.12.6 ~x86
=dev-libs/nspr-4.8.4 ~x86

  So far, so good, I've done a bit of surfing, and I'm listening to
live365.com internet radio (Flash player) whilst typing this message.
Assuming I don't run into problems during the weekend, how do I file a
stabilization request at bugzilla?  Will it be one request lumping all 4
together, or will it be 4 separate requests?

-- 
Walter Dnes <waltdnes@waltdnes.org>

Re: [gentoo-user] How to request multiple keyword removals Firefox 3.6.2?

[Justin]

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

On 25/03/10 06:09, Walter Dnes wrote:
>   Given the seriousness of the latest Firefox hole, I decided that
> keywording Firefox 3.6.2 ~x86 was less of a risk than continuing to run
> 3.5.8.  However, there were a few ~x86 ebuild dependencies on top of
> ~x86 ebuild dependencies.  My /etc/portage/package.keywords ended up
> with the following...
> 
> =www-client/mozilla-firefox-3.6.2 ~x86
> =net-libs/xulrunner-1.9.2.2-r1 ~x86
> =dev-libs/nss-3.12.6 ~x86
> =dev-libs/nspr-4.8.4 ~x86
> 
>   So far, so good, I've done a bit of surfing, and I'm listening to
> live365.com internet radio (Flash player) whilst typing this message.
> Assuming I don't run into problems during the weekend, how do I file a
> stabilization request at bugzilla?  Will it be one request lumping all 4
> together, or will it be 4 separate requests?
> 

Just file a simple bug report as normal. Only request the stabilization
of firefox and list all ~arch ebuild which are in the DEP chain in your
bug report. The bug wranglers will handle the rest.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]