Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 70574 - emerge mysteriously quits on emerge of gpgme
Summary: emerge mysteriously quits on emerge of gpgme
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Daniel Black (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-09 07:05 UTC by Timothy Miller
Modified: 2004-12-03 20:35 UTC (History)
1 user (show)

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 Timothy Miller 2004-11-09 07:05:15 UTC
I wanted to rebuild my entire system, because I'd gotten my CFLAGS wrong, so I did "emerge -e world".  emerge bailed when trying to emerge gpgme.  This is the tail of the the output:

[finishing with gnupg]
>>> original instance of package unmerged safely.
>>> app-crypt/gnupg-1.2.6 merged.

>>> clean: No packages selected for removal.

>>> emerge (193 of 267) app-crypt/gpgme-0.9.0-r1 to /


This is the corresponding bit of /var/log/emerge.log

1099992567:  >>> AUTOCLEAN: app-crypt/gnupg
1099992567:  --- AUTOCLEAN: Nothing unmerged.
1099992567:  ::: completed emerge (192 of 267) app-crypt/gnupg-1.2.6 to /
1099992567:  >>> emerge (193 of 267) app-crypt/gpgme-0.9.0-r1 to /
1099992567:  === (193 of 267) Cleaning (app-crypt/gpgme-0.9.0-r1::/usr/portage/a
pp-crypt/gpgme/gpgme-0.9.0-r1.ebuild)
1099992568:  === (193 of 267) Compiling/Merging (app-crypt/gpgme-0.9.0-r1::/usr/
portage/app-crypt/gpgme/gpgme-0.9.0-r1.ebuild)


As you can see, it just mysteriously quits.

Also, the actual command that I typed was:

emerge -e world > /tmp/emerge_log 2>&1

The emerge_log file was 61701443, but I didn't run out of space anywhere, and /tmp is just part of the root file system.

As I'm sure you can imagine, given the number of packages to emerge, it would be very frustrating to start all over again, just to have it fail again.

Reproducible: Didn't try
Steps to Reproduce:
1.
2.
3.
Comment 1 Gregorio Guidi (RETIRED) gentoo-dev 2004-11-09 14:35:29 UTC
You can try 'emerge --resume' to avoid starting from the beginning.
Comment 2 Timothy Miller 2004-11-09 20:12:23 UTC
Every other place I've read has said that "emerge --resume" doesn't work for "emerge -e world".
Comment 3 Daniel Black (RETIRED) gentoo-dev 2004-11-14 06:03:35 UTC
move the entries in /var/lib/portage/world from gpgme onwards to a different file.

Then you can use: cat {file}  | xargs -n1 emerge 

As for a problem with gpgme? I can't see one. Try removing /var/tmp/portage/* before reemerging.
Look for system error messages - dmesg or /var/log/{message,everything/current}

If it sounds like I have no idea - your right.
Comment 4 Timothy Miller 2004-11-14 12:31:44 UTC
The bug isn't with gpgme.  The bug is that emerge should never quit mysteriously with no messages.  There should not be a way for emerge to terminate without saying SOMETHING about why it quit.
Comment 5 Daniel Black (RETIRED) gentoo-dev 2004-12-03 20:35:13 UTC
I need more info to analyse this like the output at the time. I'm guess you have got past this point somehow. If this does reoccur somehow I am interested.