Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 20089 - emerge -u xfree (xfree 4.3.0 r2) fails
Summary: emerge -u xfree (xfree 4.3.0 r2) fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: PPC Linux
: High normal (vote)
Assignee: PPC Porters
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-28 01:10 UTC by Adik Gede
Modified: 2006-02-04 06:03 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adik Gede 2003-04-28 01:10:16 UTC
emerge xfree
fetches XFree86-4.3.0-patches-1.1.2.tar.bz2

exits

!!failure unpacking XFree86-4.3.0-patches-1.1.3.tar.bz2


Reproducible: Always
Steps to Reproduce:
1.emerge xfree


Actual Results:  
emerge xfree
fetches XFree86-4.3.0-patches-1.1.2.tar.bz2

exits

!!failure unpacking XFree86-4.3.0-patches-1.1.3.tar.bz2

Expected Results:  
updated xfree
Comment 1 Graham Forest 2003-04-28 01:14:25 UTC
Please make sure you're running the latest version of portage, then run emerge xfree again, and post the emerge output. Thanks.
Comment 2 Adik Gede 2003-04-28 03:11:18 UTC
I downloaded XFree86-4.3.0-patches-1.1.3.tar.bz2 to /usr/portage/distfiles/
and ran emerge -u xfree again so its busy at the moment.

portage is current.

The error message was more or less:
unpacking XFree86-4.3.0-patches-1.1.3.tar.bz2

exitcode 2

failed to unpack XFree86-4.3.0-patches-1.1.3.tar.bz2


If I look in the ebuild for xfree 4.3.0 rc2 it specs patch level 1.1.3

but if I look in digest-xfree-4.3.0-r2 it lists XFree86-4.3.0-patches-1.1.2.tar.bz2

Do you think it might be the inconsistancy between the digest and the ebuild files?
Comment 3 Luca Barbato gentoo-dev 2003-06-08 17:23:24 UTC
please sync again, and emerge the -r3

make sure you have enough space to unpack everything.
Comment 4 Luca Barbato gentoo-dev 2003-06-28 13:20:05 UTC
closed for no user response.

Please reopen the bug if it still apply (should not)