Bug 136285 – portage-2.1 not proper log handling

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Piotr Jaroszyński (RETIRED) 2006-06-10 07:04:48 UTC]

$ ebuild parano-0.3.3.ebuild install
$ cat /var/cache/edb/counter
7713
$ la /var/log/portage/7714-parano-0.3.3.log
-rw-r--r-- 1 peper portage 9.5K Jun 10 15:57 /var/log/portage/7714-parano-0.3.3.log

$ su

# ebuild parano-0.3.3.ebuild qmerge
# cat /var/cache/edb/counter
7714
# la /var/log/portage/7715-parano-0.3.3.log
-rw-r--r-- 1 root portage 448 Jun 10 15:59 /var/log/portage/7715-parano-0.3.3.log

# ebuild parano-0.3.3.ebuild unmerge
# cat /var/cache/edb/counter
7714
# la /var/log/portage/7715-parano-0.3.3.log
-rw-r--r-- 1 root portage 946 Jun 10 16:02 /var/log/portage/7715-parano-0.3.3.log

# logout

$ ebuild parano-0.3.3.ebuild install
tee: /var/log/portage/7715-parano-0.3.3.log: Permission denied

[Comment 1 Zac Medico 2006-06-10 13:41:15 UTC]

Perhaps we should encode the creation time of PORTAGE_BUILDDIR into the log name, in addition to the counter.  That will allow the same log to be used in separate ebuild invocations that use the same build dir.

[Comment 2 Zac Medico 2006-06-12 22:53:18 UTC]

It seems that it's not possible to get a constant timestamp from $PORTAGE_BUILDDIR itself, so maybe we should use a hidden file inside of it to identify the log file.  Perhaps $PORTAGE_BUILDDIR/.logid is good?  It could just be an empty file and we could use it's UTC timestamp to generate the log file name.  For the name of the log file, we could borrow the format used by pym/elog_modules/mod_save.py:

${CATEGORY}:${PN}-${PVR}:%Y%m%d-%H%M%S.log

[Comment 3 Piotr Jaroszyński (RETIRED) 2006-06-13 02:25:13 UTC]

sounds good to me ;]

[Comment 4 Zac Medico 2006-06-13 12:56:37 UTC]

This is fixed in svn r3506.

[Comment 5 Zac Medico 2006-06-16 10:03:20 UTC]

This has been released in 2.1.1_pre1.