From: Jani Monoses <jani@iv.ro>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] emerge harmless buglet?
Date: Mon, 4 Aug 2003 16:03:01 +0300 [thread overview]
Message-ID: <20030804160301.713ebda7.jani@iv.ro> (raw)
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 /
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-08-04 12:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 13:03 Jani Monoses [this message]
2003-08-04 13:32 ` [gentoo-dev] emerge harmless buglet? Marius Mauch
2003-08-04 14:34 ` splite-gentoo
2003-08-04 19:52 ` Mike Frysinger
2003-08-04 20:28 ` splite-gentoo
2003-08-04 22:15 ` Mike Frysinger
2003-08-04 22:20 ` Aron Griffis
2003-08-04 22:43 ` Mike Frysinger
2003-08-05 2:07 ` Aron Griffis
2003-08-05 2:11 ` Mike Frysinger
2003-08-05 2:55 ` Aron Griffis
2003-08-04 22:31 ` splite-gentoo
2003-08-05 2:28 ` Marius Mauch
2003-08-05 9:00 ` Paul de Vrieze
2003-08-05 10:43 ` Spider
2003-08-05 15:29 ` Donny Davies
2003-08-05 19:05 ` Spider
2003-08-05 16:05 ` Aron Griffis
2003-08-05 16:54 ` Robin H.Johnson
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=20030804160301.713ebda7.jani@iv.ro \
--to=jani@iv.ro \
--cc=gentoo-dev@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