Re: [gentoo-dev] emerge harmless buglet?

[Marius Mauch <genone@genone.homeip.net>]

On 08/04/03  Jani Monoses wrote:

> With latest stable portage I always get errors like below while
> emerging packages. 
> Changing a line in portage.py makes this go away.Whether spawn is not
> supposed to be used with a multiple commands piping eachother I don't
> know but anyway isn't using bunzip2 easier ?
> 
> at line 4775 :
>         print ">>> extracting",mypkg
> #       notok=spawn("cat "+mytbz2+"| bzip2 -dq | tar xpf -",free=1)
>         notok=spawn("bunzip2 -q "+mytbz2, free=1)
> 
> The borken pipe error is there at every emerge.
> 
> i.e
> >>> extracting info
> >>> extracting gcc-config-1.3.3-r1
> cat: write error: Broken pipe
> >>> Merging sys-devel/gcc-config-1.3.3-r1 to /


It's fixed in current 49_pre versions. And only using bunzip2 won't work
as it only decompresses the package, but it does not untar it. You have
to send the uncompressed tarball to tar. The fixed line is
	notok=spawn("bzip2 -dc "+mytbz2+" | tar xpf -",free=1)

Marius

-- 
Public Key at http://www.genone.de/info/gpg-key.pub

In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.

--
gentoo-dev@gentoo.org mailing list