>From Dhruba Bandopadhyay <[EMAIL PROTECTED]>:
First, delete the distfile and try to re-emerge. If no luck, do
it
manually.
ebuild /path/to/ebuild unpack | tar -xjf <package> into
/var/tmp/portage/portage-2.0.48-r2/work
ebuild /path/to/ebuild compile
ebuild /path/to/ebuild merge
Or file a bug and wait for it to be fixed globally. That
package is
hardmasked anyway isn't it?
On Tue, 2003-07-01 at 18:47, bryce wrote:
> OK, i got caught up in this little bug that has been passed around, and
> now they want me to downgrade portage... and i would love to, but i get
> this error when i try( and w/ some other packages as well):
>
> >>> Unpacking source...
> >>> Unpacking portage-2.0.48-r1.tar.bz2 to
> /var/tmp/portage/portage-2.0.48-r1/wo
> rk
> Calculating dependencies ...done!
> >>> emerge (1 of 1) sys-apps/portage-2.0.48-r1 to /
> >>> md5 src_uri ;-) portage-2.0.48-r1.tar.bz2
> (1 of 1) Compiling/Merging
> (/usr/portage/sys-apps/portage/portage-2.0.48-r1.ebu
> ild)tar: This does not look like a tar archive
> tar: Skipping to next header
> tar: Archive contains obsolescent base-64 headers
> tar: Error exit delayed from previous errors
>
> bzip2: I/O or other error, bailing out. Possible reason follows.
> bzip2: Broken pipe
> Input file = /usr/portage/distfiles/portage-2.0.48-r1.tar.bz2,
> output fi
> le = (stdout)
>
> !!! ERROR: sys-apps/portage-2.0.48-r1 failed.
> !!! Function unpack, Line 294, Exitcode 2
> !!! failure unpacking portage-2.0.48-r1.tar.bz2
>
> I tried whipping out the install cd, and doing it from in there, but no
> luck, tried reemerging tar see if that helped, tried remergin bzip2(
> and that just utterly failed).
>
> Any ideas???
>
> Thanks in advance,
> bryce
>
>
> --
> [EMAIL PROTECTED] mailing list
>
--
[EMAIL PROTECTED] mailing list
