Hello, I noticed a strange thing. Compare the two following lines: layman -S && emerge --sync && egencache --repo=local --update && emerge --regen && eix-remote update && eix-update layman -S && emerge --sync && egencache --repo=local --update && ( emerge --regen || echo "“emerge --regen” returned the error status $?." ) && eix-remote update && eix-update The second one goes trough to the end. The first one stops after “emerge --regen”. This is a problem, since (those lines are usually, what a complete eix-sync does [trough the .conf], and) eix-sync depends on a non-error return status. This is reproducible. If you have trouble reproducing it, just ask, and we will find the relevant difference in the systems. Reproducible: Always Steps to Reproduce:
Does emerge --regen spew out any errors? I would suspect that you have some badness in one of your overlays, and if any single ebuild fails to have its metadata regenerated the return code of course becomes nonzero ...
Aaah, allright. That might be it. Quality on some overlays is a bit shoddy. I have to toggle quiet mode, and then we’ll see. Let’s close this bug, and let it stand here for anyone who will have the same problem. :) What is the “WORKSASINTENDED” resolution? ^^ Thank you for your time.
