Bug 183167

Summary:	Portage elog functionality does not work with emerge -B or -K
Product:	Portage Development	Reporter:	Jeff Fernandez <j1>
Component:	Unclassified	Assignee:	Portage team <dev-portage>
Status:	RESOLVED FIXED
Severity:	normal	Keywords:	InVCS
Priority:	High
Version:	2.1
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	181949
Attachments:	explicitly call elog_process() when --buildpkgonly is enabled

Description Jeff Fernandez 2007-06-25 16:14:16 UTC

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

Comment 1 Zac Medico gentoo-dev

2007-06-25 19:48:45 UTC

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.

Comment 2 Jeff Fernandez 2007-06-25 23:49:55 UTC

(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!

Comment 3 Zac Medico gentoo-dev

2007-06-29 02:55:09 UTC

This has been released in 2.1.3_rc6.