Summary: | emerge mysteriously quits on emerge of gpgme | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Timothy Miller <theosib> |
Component: | New packages | Assignee: | Daniel Black (RETIRED) <dragonheart> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | greg_g |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Timothy Miller
2004-11-09 07:05:15 UTC
You can try 'emerge --resume' to avoid starting from the beginning. Every other place I've read has said that "emerge --resume" doesn't work for "emerge -e world". 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. 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. 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. |