On Sun, Jul 28, 2019 at 9:31 AM Neal Gompa <ngompa13(a)gmail.com> wrote:
On Sun, Jul 28, 2019 at 9:27 AM Björn Persson <Bjorn(a)xn--rombobjrn-67a.se> wrote:
> In a package review I came across a changelog entry in this format:
> * Thu Jul 25 12:24:56 CEST 2019 Name <nn(a)example.com> - 0.1.0-1
> RPM appears to be able to parse that, but the time of day and the
> timezone code aren't in the format prescribed by the Packaging
> Guidelines. On the other hand it's not clear that the policy is meant
> to explicitly forbid such precise timestamps, as it seems mostly
> concerned with the placement of the version and release:
> Does the policy need to be updated to allow a time of day and a timezone
> code? Or does it need to be clarified to clearly forbid them?
> Ideally the date/time format variants that RPM accepts should be
> documented somewhere – in a spec file syntax specification perhaps – and
> the guidelines should point to that specification.
This is a new changelog format supported since RPM 4.14.
It was added in this commit:
It is supported in all released versions of Fedora, and it is supported in EL8.
Since many of us still use RHEL and CentOS 6 and 7 as targets of
backported Fedora tools, why would we want to even use time of day?
RPM is such a critical system for legacy and supported releases I'd be
extremely reluctant to expect them to be compatible with what is
essentially an extraneous feature, namely the support of timestamps in
changelogs where they serve no significant functional use. Why publish