Description of problem: See http://oss.sgi.com/pipermail/pcp/2016-July/010948.html for background. - pmdumptext(1) reports time/zone incorrectly as reported above - pmchart(1) is incorrect like pmdumptext(1) but additionally the time controls it shows are using times as if -z had been given (so in the case of pcp-vmstat/EET-2 mentioned in the referenced email above, 06:53 is expected but pmchart shows 07:53 and 15:53) - pmcollectl(1) reports current local time not the archive time I haven't checked pmdiff(1), pmie(1), pminfo(1), pmlogcheck(1) or most of the pcp(1) subcommands. pmclient(1), pmiostat(1), pmlogsummary(1), pmstat(1) seem to handle this ok.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
Some related findings: https://groups.io/g/pcp/topic/6243856#17044 Might be best to continue this in upstream.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Hey Marko, (In reply to Marko Myllynen from comment #4) > Some related findings: > > https://groups.io/g/pcp/topic/6243856#17044 > > Might be best to continue this in upstream. Given your comments upstream, would be appropriate to let this bug close, EoL? Or reopen to Rawhide?
I'd say let's close this, the issue was a corner case rabbit hole and if further discussion is warranted, that can happen in the upstream thread and/or upstream tickets. Thanks.