Today I made a large update which resulted in a lot of preserved libs being made. Not thinking much, I logged out of the root shell only to find that I couldn't log back in because I didn't do etc-update (bug 412721), so I was effectively locked myself out of the system. The problem is that I didn't see it because I would have needed to scroll up. A simple solution is to make the etc-update message after the preserved-libs message, since it's less verbose and usually much more important. (On a related note, is it possible to get an email sent when I need to etc-update?) Reproducible: Always
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=92a8357ca98d4a42e7747abd2cf4b390381fc6bc (In reply to comment #0) > (On a related note, is it possible to get an email sent when I need to > etc-update?) Sure we could do that. We already have support for sending mail in the elog mail module.
That was fast, thanks! I already have PORTAGE_ELOG_CLASSES="warn error log", and I get messages from packages, but I never got anything telling me if I have configuration files in /etc to update (Sorry if I'm missing something!)
(In reply to comment #2) > I already have PORTAGE_ELOG_CLASSES="warn error log", and I get messages > from packages, but I never got anything telling me if I have configuration > files in /etc to update (Sorry if I'm missing something!) Yeah, it doesn't send mails for that yet. You can get elog messages mailed if you do this though: PORTAGE_ELOG_SYSTEM="${PORTAGE_ELOG_SYSTEM} mail"
This is fixed in 2.1.10.57 and 2.2.0_alpha101.
