Bug 925613

Summary:	sys-apps/portage: emerge produces logs that do not belong to a package
Product:	Portage Development	Reporter:	Agostino Sarubbo <ago>
Component:	Core - Interface (emerge)	Assignee:	Portage team <dev-portage>
Status:	CONFIRMED ---
Severity:	major	CC:	zmedico
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	377365
Attachments:	tkimg-1.4.16:20240227-123830.log openpgp-keys-russallbery-20230000:20240227-124353.log

Description Agostino Sarubbo gentoo-dev

2024-02-27 12:48:26 UTC

While a package cannot be merged because of a fetch failure or because 'Filesize does not match recorded size', emerge produces a log that is not traceable to any package, thus making tinderbox become a war.

Is possible to write those logs in a way like:

 * Package:    ...
 * Repository: ...
 * Maintainer: ...
 * USE:        ...
 * FEATURES:   ...

?

I'm attaching both examples.

Comment 1 Agostino Sarubbo gentoo-dev

2024-02-27 12:48:51 UTC

Created attachment 886116 [details]
tkimg-1.4.16:20240227-123830.log

tkimg-1.4.16:20240227-123830.log

Comment 2 Agostino Sarubbo gentoo-dev

2024-02-27 12:49:09 UTC

Created attachment 886117 [details]
openpgp-keys-russallbery-20230000:20240227-124353.log

openpgp-keys-russallbery-20230000:20240227-124353.log

Comment 3 Mike Gilbert gentoo-dev

2024-03-04 17:13:25 UTC

To point out the obvious: the package is in the log file name.

Comment 4 Mike Gilbert gentoo-dev

2024-03-04 17:19:56 UTC

Anyway, I imagine it should be possible to prefix the logs with the standard info.