Hello, there is a problem with emerge --regen, the message mentioned in the summary, and the exit status: When you run emerge --regen, and this message occurs, emerge returns with an error exit status. This causes programs like eix-sync to stop furter work and exit too. Especially when running it from a file inside /etc/cron.*/. Because the message not really is an error, and there are no problems when this message occurs, emerge should not give back an error, so that eix-sync can continue to do its work. Reproducible: Always Steps to Reproduce: 1. Have “app-portage/eix” installed. 2. Add “@@emerge --regen” to “/etc/eix-sync.conf” (after the “*”). 3. Run “eix-sync” Actual Results: eix-sync exits right after the successful regen, and never actually executes the required eix-update that it has to do at the end. Which leaves eix in a improper state. This is *not* a problem of eix-sync, because it correctly exits when one of the executed programs exits with an error. It expects that one command depends on previous commands. Wich happens to be true in this case. Expected Results: emerge should not treat the messages as errors, and return with a non-error exit status, indicating success. Alternatively, the problem with the SIGQUIT handlers should be fixed, so that the message only occurs on actual errors. Of course this is a problem which only occurs in the teamwork of the sandbox, emerge and eix-sync. But it can only be fixed, if all three programs' maintainers work together. Not by everyone blaming the others. :)
Please ignore this bug, and look at bug #289486 instead. This one was a result of an error in bugzilla.
let's dupe it
*** This bug has been marked as a duplicate of bug 289486 ***
