public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Justin <justin@j-schmitz.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to request multiple keyword removals Firefox 3.6.2?
Date: Thu, 25 Mar 2010 08:11:09 +0100	[thread overview]
Message-ID: <4BAB0C8D.5010108@j-schmitz.net> (raw)
In-Reply-To: <20100325050950.GB4246@waltdnes.org>

[-- 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 --]

      reply	other threads:[~2010-03-25  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  5:09 [gentoo-user] How to request multiple keyword removals Firefox 3.6.2? Walter Dnes
2010-03-25  7:11 ` Justin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BAB0C8D.5010108@j-schmitz.net \
    --to=justin@j-schmitz.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox