727100 – portage: add timestamp of the sync in the build log

Bug 727100 - portage: add timestamp of the sync in the build log

Summary: portage: add timestamp of the sync in the build log

Status:	CONFIRMED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Enhancement/Feature Requests (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2020-06-04 10:40 UTC by Agostino Sarubbo
Modified:	2020-06-04 10:40 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Agostino Sarubbo gentoo-dev

2020-06-04 10:40:48 UTC

Atm, the timestamp is included in emerge --info.

The first thing to point out is that in case / is in chroot, portage fails to detect if it is a git or rsync tree and reads only /etc/portage/repos.conf/

In case of tinderboxes, where they compile 24/7 it may happen that there are synces between the generation of build log and generation of emerge --info, so a good idea would be put the timestamp of the sync directly in the build log as it can help maintainers to detect if an issue is a duplicate or if an issue still persists after the sync.

Would be also helpful print the URL of the git mirror, to detect if it is a gentoo-mirror (https://github.com/gentoo-mirror/gentoo) or this is directly our git repo (https://gitweb.gentoo.org/repo/gentoo.git/)

Thanks