Summary: | genlop reports incorrect time of emerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Christophe <cjouny> |
Component: | Current packages | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED UPSTREAM | ||
Severity: | minor | CC: | giorgio, mips |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Christophe
2004-03-18 07:37:13 UTC
Forgot to mention version genlop-0.16.3 Bug was fixed by changes in genlop-0.20.2. Sorry about noise. Works for amd64 too. Keyword amd64 could be added to genlop. Can you emerge splat and check if it has the same problem ? Thanks for CC'ing me. About the difference of 5 hours, genlop since 0.16.3 used gmtime() which reports time in GMT. genlop 0.20 and above use localtime() by default. About the difference of few minutes: genlop displays *end* time of an ebuild merge; the timestamp the bug reporter read in /var/log/emerge.log is the start one. Giorgio Tested on amd64, splat-0.07 works fine. Can someone test it on mips so I can close this bug ? try e-mailing upstream, we dont maintain this package [giorgio@mysite@org] |