When doing an "emerge --config" the einfo (presumably elog, ewarn, ..., too) messages are not written to an elog file in /var/log/portage/elog/ like it is done in all other ebuild phases. Reproducible: Always Steps to Reproduce: The simplest test that doesn't change anything in your system would be: 1. emerge --config sys-libs/timezone-data 2. elogv Actual Results: Step 1 writes " * Assuming your /etc/localtime symlink is what you want; skipping update." on the screen and into a file in /var/log/portage/ but no elog file. Step 2 says: There aren't any elog files on /var/log/portage/elog Expected Results: Step 1 writing an elog file. Step 2 showing the elog file with the message.
Please share the output of the following command: portageq envvar PORTAGE_ELOG_CLASSES
einfo messages are only saved to the /var/log/portage/elog directory if PORTAGE_ELOG_CLASSES contains "info". The default setting for PORTAGE_ELOG_CLASSES is "log warn error". Please re-open if you can reproduce the issue with "info" in PORTAGE_ELOG_CLASSES.
(In reply to Mike Gilbert from comment #1) > Please share the output of the following command: > > portageq envvar PORTAGE_ELOG_CLASSES The output is info log warn error qa
