From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Portage and SIGHUP
Date: Thu, 23 Apr 2009 14:23:41 +0200 [thread overview]
Message-ID: <20090423122341.GO15099@gentoo.org> (raw)
I recently noticed this:
(pegasus:portage/dev-libs/poppler) fabian% emerge --resume
Calculating dependencies... done!
*** Resuming merge...
>>> Verifying ebuild manifests
>>> Starting parallel fetch
>>> Emerging (1 of 9) dev-libs/libgpg-error-1.7
* libgpg-error-1.7.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking libgpg-error-1.7.tar.bz2 to /net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/var/tmp/portage/dev-libs/libgpg-error-1.7/work
* Running eautoreconf in '/net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/var/tmp/portage/dev-libs/libgpg-error-1.7/work/libgpg-error-1.7' ...
* Running aclocal -I m4 -I /net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/share/aclocal ...
Hangup
(pegasus:portage/dev-libs/poppler) fabian%
e.g. Portage terminating immediately on a SIGHUP. If I sent SIGHUP myself to
Portage from another shell it immediately stops as well.
Can some one Linux try to reproduce this? I tested it by doing emerge -av portage and from another terminal SIGHUP that emerge.
--
Fabian Groffen
Gentoo on a different level
next reply other threads:[~2009-04-23 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 12:23 Fabian Groffen [this message]
2009-04-23 17:52 ` [gentoo-portage-dev] Portage and SIGHUP Zac Medico
2009-05-05 6:26 ` [gentoo-portage-dev] files in ${FILESDIR} Toha
2009-05-05 6:34 ` Mike Frysinger
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=20090423122341.GO15099@gentoo.org \
--to=grobian@gentoo.org \
--cc=gentoo-portage-dev@lists.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