From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Firefox 3.0.12 emerge dies
Date: Mon, 27 Jul 2009 16:05:35 -0700 [thread overview]
Message-ID: <5bdc1c8b0907271605n1a8aaa86le2a1133c55c5f0bf@mail.gmail.com> (raw)
In-Reply-To: <h4l75c$tjs$1@ger.gmane.org>
On Mon, Jul 27, 2009 at 2:46 PM, walt<w41ter@gmail.com> wrote:
> On 07/27/2009 02:08 PM, Mark Knecht wrote:
>>
>> On Mon, Jul 27, 2009 at 5:57 AM, walt<w41ter@gmail.com> wrote:
>>>
>>> On 07/26/2009 01:25 PM, Walter Dnes wrote:
>>>>
>>>> I've been unsuccessfully trying to build the latest security patch
>>>> version of Firefox 3.0. I keep getting the same error message after
>>>> 3 days of re-syncing and retrying. The build dies early on in the
>>>> patch-appliaction stage, so log.txt is small. The error message also
>>>> mentioned to include the contents of the patch ".out" file, which I have
>>>> done as log2.txt. Any ideas?
>>>
>>> My ~amd64 machine skipped that version and went to 3.5.1 instead.
>>> Is there a particular reason you don't want to do that?
>>>
>>
>> Possibly because it's not marked stable?...
>
> 3.0.12 is also marked unstable, so I assumed that Walter (the other one)
> is running an unstable gentoo. Because these rapid updates to firefox
> are all security patches it would be nice to get the latest one...
Yeah, I agree. I wanted 3.0.12 also as 3.0.11 apparently has a
security bug but I felt like 3.5 was probably a jump to big.
Cheers,
Mark
next prev parent reply other threads:[~2009-07-27 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 20:25 [gentoo-user] Firefox 3.0.12 emerge dies Walter Dnes
2009-07-27 12:57 ` [gentoo-user] " walt
2009-07-27 21:08 ` Mark Knecht
2009-07-27 21:46 ` walt
2009-07-27 23:05 ` Mark Knecht [this message]
2009-07-28 0:52 ` Walter Dnes
2009-07-29 2:31 ` [gentoo-user] " Walter Dnes
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=5bdc1c8b0907271605n1a8aaa86le2a1133c55c5f0bf@mail.gmail.com \
--to=markknecht@gmail.com \
--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