I have elog set up in make.conf like this: PORTAGE_ELOG_CLASSES="info qa warn error log" PORTAGE_ELOG_SYSTEM="save mail_summary" PORTAGE_ELOG_MAILURI="user@some.mailserver.com" This produces mails and logs during normal emerges. However, when using emerge -K or -B, no elog logs or mails are produced. This behavior, I believe, defeats the purpose of Portage elog. It should be possible to build packages unattended with -B, and then merge them to the system later with -K after reviewing the elog output. Reproducible: Always Steps to Reproduce: 1. Configure elog in make.conf 2. Build a package with emerge -B 3. Merge the package with emerge -K 4. Observe the lack of elog output
Created attachment 123070 [details, diff] explicitly call elog_process() when --buildpkgonly is enabled This should fix it. The -K option alone doesn't affect elog, but -B certainly does.
(In reply to comment #1) > Created an attachment (id=123070) [edit] > explicitly call elog_process() when --buildpkgonly is enabled > > This should fix it. The -K option alone doesn't affect elog, but -B certainly > does. > That patch fixed the problem. Thanks!
This has been released in 2.1.3_rc6.
