208866 – elog system save_summary should save dates in local time or specify the timezone

Bug 208866 - elog system save_summary should save dates in local time or specify the timezone

Summary: elog system save_summary should save dates in local time or specify the timezone

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All Linux

Importance:	Lowest enhancement (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:	200044
	Show dependency tree

Reported:	2008-02-04 17:26 UTC by Denilson Sá Maia
Modified:	2008-02-12 17:09 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 Denilson Sá Maia 2008-02-04 17:26:54 UTC

When we have "save_summary" in PORTAGE_ELOG_SYSTEM variable (which is the default for some months now), portage stores a summary of elog messages at /var/log/portage/elog/summary.log. See a sample header line from that file:

>>> Messages generated by process 23432 on 2008-02-04 17:17:07 for package sys-libs/pam-0.99.9.0:

The time written right there is UTC time, but I think this was not expected.
/var/log/messages stores time in local time.
Apache logs are also in local time, but they include timezone information: [04/Feb/2008:15:16:31 -0200]

So, my suggestion is to either use local time, or at least add timezone information to the timestamp of elog. Or, even better, do both.

Comment 1 Arfrever Frehtes Taifersar Arahesis (RETIRED) gentoo-dev

2008-02-12 15:28:11 UTC

Fixed in r9273 (trunk) and r9303 (branches/2.1.2).
Released in portage-2.1.4.2.

This bug should block Bug #200044.