Bug 281174 – emerge does not log collisions sys-apps/portage-2.2_rc12 PORT_LOG build collision-protect protect-owned

• Product: Portage Development
• Status: RESOLVED FIXED

[Description daid kahl 2009-08-12 06:30:11 UTC]

If FEATURES collision-protect or protect-owned (on by default) are turned on, then any emerge which over-writes existing files fails; we all expect this behavior.  However, in the portage build logs for that emerge, the collision summary itself is not logged.  In the case of a collision, the last thing written to the log is Checking X files for collisions.  However, stdout is sent a list of files the package would over-write, and an emerge failure message.  In order to safely and successfully complete the merge, it is critical to know which files are colliding, so this information should be logged.

I request that all the information sent to stdout by emerge, specifically about file collisions, is also sent to the portage build log.  In some cases, it is not possible to access the stdout collision error (scrollback buffer too small, system reboot, etc), and this makes solving the collision error more difficult without proper logging.

Reproducible: Always

Steps to Reproduce:
1. Emerge a package that over-writes existing files with the FEATURES collision-protect or protect-owned enabled.
2. Check the log file corresponding to the package and build date in PORT_LOGDIR.
3. Observe no specific details of the collision have been logged.

Actual Results:  
The portage log does not tell me which files would be over-written by the emerge in the case of a collision.

Expected Results:  
The portage log is a verbatim copy of the messaging sent to stdout by emerge, which includes the details of a failed emerge due to a collision.

[Comment 1 daid kahl 2009-08-12 06:57:51 UTC]

I should be looking in PORT_LOGDIG/elog

Sorry!