[gentoo-user] Firefox 3.0.12 emerge dies

[gentoo-user] Firefox 3.0.12 emerge dies

[Walter Dnes]

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

  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?

-- 
Walter Dnes <waltdnes@waltdnes.org>

[-- Attachment #2: log.txt --]
[-- Type: text/plain, Size: 3631 bytes --]

 ^[[32;01m*^[[0m You are enabling official branding. You may not redistribute this build
 ^[[32;01m*^[[0m to any users on your network or the internet. Doing so puts yourself into
 ^[[32;01m*^[[0m a legal problem with Mozilla Foundation
 ^[[32;01m*^[[0m You can disable it by emerging mozilla-firefox _with_ the bindist USE-flag
>>> Unpacking source...
>>> Unpacking xulrunner-1.9.0.12.tar.bz2 to /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work
>>> Unpacking mozilla-firefox-3.0.12.tar.bz2 to /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work
>>> Unpacking mozilla-firefox-3.0.12-patches-0.1.tar.bz2 to /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work
>>> Source unpacked in /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work
>>> Preparing source in /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work/mozilla ...
 ^[[32;01m*^[[0m Applying various patches (bugfixes/updates) ...
 ^[[32;01m*^[[0m   000_flex-configure-LANG.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   001-firefox_gentoo_install_dirs.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   003-bz386904_config_rules_install_dist_files.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   005-installer_shouldnt_copy_xulrunner.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   020_noxul-mips-asm.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   021_noxul-mips-fpic.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   030-firefox_encode_spaces.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   055_firefox-2.0_gfbsd-pthreads.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   063_firefox-rpath-3.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   064_noxul-nsplugins-v3.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   068_noxul-nss-gentoo-fix.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   085-arm-gcc42.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   090-unaligned.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m   097_noxul_glibc-maxpathlen.patch ...

 ^[[31;01m*^[[0m Failed Patch: 097_noxul_glibc-maxpathlen.patch !
 ^[[31;01m*^[[0m  ( /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work/patch/097_noxul_glibc-maxpathlen.patch )
 ^[[31;01m*^[[0m 
 ^[[31;01m*^[[0m Include in your bugreport the contents of:
 ^[[31;01m*^[[0m 
 ^[[31;01m*^[[0m   /var/tmp/portage/www-client/mozilla-firefox-3.0.12/temp/097_noxul_glibc-maxpathlen.patch-6570.out

 ^[[31;01m*^[[0m 
 ^[[31;01m*^[[0m ERROR: www-client/mozilla-firefox-3.0.12 failed.
 ^[[31;01m*^[[0m Call stack:
 ^[[31;01m*^[[0m               ebuild.sh, line   49:  Called src_prepare
 ^[[31;01m*^[[0m             environment, line 3291:  Called epatch '/var/tmp/portage/www-client/mozilla-firefox-3.0.12/work/patch'
 ^[[31;01m*^[[0m             environment, line 1747:  Called die
 ^[[31;01m*^[[0m The specific snippet of code:
 ^[[31;01m*^[[0m                   die "Failed Patch: ${patchname}!";
 ^[[31;01m*^[[0m  The die message:
 ^[[31;01m*^[[0m   Failed Patch: 097_noxul_glibc-maxpathlen.patch!
 ^[[31;01m*^[[0m 
 ^[[31;01m*^[[0m If you need support, post the topmost build error, and the call stack if relevant.
 ^[[31;01m*^[[0m A complete build log is located at '/var/log/portage/www-client:mozilla-firefox-3.0.12:20090726-200847.log'.
 ^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/www-client/mozilla-firefox-3.0.12/temp/environment'.
 ^[[31;01m*^[[0m 

[-- Attachment #3: log2.txt --]
[-- Type: text/plain, Size: 3006 bytes --]

***** 097_noxul_glibc-maxpathlen.patch *****

============================================

PATCH COMMAND:	 patch -p0 -g0 -E --no-backup-if-mismatch < /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work/patch/097_noxul_glibc-maxpathlen.patch

============================================
patching file xpcom/build/nsXPCOMPrivate.h
Hunk #1 FAILED at 231.
1 out of 1 hunk FAILED -- saving rejects to file xpcom/build/nsXPCOMPrivate.h.rej
============================================

PATCH COMMAND:	 patch -p1 -g0 -E --no-backup-if-mismatch < /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work/patch/097_noxul_glibc-maxpathlen.patch

============================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- xpcom/build/nsXPCOMPrivate.h.old	Tue Oct 21 16:36:29 2008 +1300
|+++ xpcom/build/nsXPCOMPrivate.h	Mon Oct 20 22:55:57 2008 -0500
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
============================================

PATCH COMMAND:	 patch -p2 -g0 -E --no-backup-if-mismatch < /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work/patch/097_noxul_glibc-maxpathlen.patch

============================================
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- xpcom/build/nsXPCOMPrivate.h.old	Tue Oct 21 16:36:29 2008 +1300
|+++ xpcom/build/nsXPCOMPrivate.h	Mon Oct 20 22:55:57 2008 -0500
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
============================================

PATCH COMMAND:	 patch -p3 -g0 -E --no-backup-if-mismatch < /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work/patch/097_noxul_glibc-maxpathlen.patch

============================================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- xpcom/build/nsXPCOMPrivate.h.old	Tue Oct 21 16:36:29 2008 +1300
|+++ xpcom/build/nsXPCOMPrivate.h	Mon Oct 20 22:55:57 2008 -0500
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
============================================

PATCH COMMAND:	 patch -p4 -g0 -E --no-backup-if-mismatch < /var/tmp/portage/www-client/mozilla-firefox-3.0.12/work/patch/097_noxul_glibc-maxpathlen.patch

============================================
missing header for unified diff at line 3 of patch
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- xpcom/build/nsXPCOMPrivate.h.old	Tue Oct 21 16:36:29 2008 +1300
|+++ xpcom/build/nsXPCOMPrivate.h	Mon Oct 20 22:55:57 2008 -0500
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored

[gentoo-user] Re: Firefox 3.0.12 emerge dies

[walt]

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?

Re: [gentoo-user] Re: Firefox 3.0.12 emerge dies

[Mark Knecht]

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?

After your post I looked at emerging it on my amd64 machine but it
requires that I start emerging other testing packages so I decided why
bother? I'll wait.

- Mark

[gentoo-user] Re: Firefox 3.0.12 emerge dies

[walt]

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...

Re: [gentoo-user] Re: Firefox 3.0.12 emerge dies

[Mark Knecht]

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

Re: [gentoo-user] Re: Firefox 3.0.12 emerge dies

[Walter Dnes]

On Mon, Jul 27, 2009 at 02:46:55PM -0700, walt wrote
>
> 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...

  Contrary to what some people may say, I'm quite quite stable <G>, and
so is my Gentoo system.  But I do enable a few security patches early by
keywording the specific build before it gets moved to stable.  Right now
I'm using Opera temporarily.

-- 
Walter Dnes <waltdnes@waltdnes.org>

Re: [gentoo-user] Firefox 3.0.12 emerge dies

[Walter Dnes]

On Sun, Jul 26, 2009 at 04:25:19PM -0400, 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?

  I finally gave up waiting, unmerged Firefox, keyworded version 3.0.12
of Firefox-bin, and emerged that without incident.  The install
automatically created a symlink from firefox-bin to firefox, and it
launches just like before.  I'll switch to 3.5.x when support for 3.0.x
is dropped.

-- 
Walter Dnes <waltdnes@waltdnes.org>