There ought to be a doc on "lifecycle of a timestamp"....
I'm willing to help if we don't already have one.
Tldr
there are various levels of abstraction when it comes to representing time. Developers overlook the details until something like this happens.
System clocks don't know about locales, dates and timezones. So the discrepancy may be due to the config of whatever container was doing the logging.
On Sun, May 7, 2023, 12:49 PM Kevin Kofler via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Chris Adams wrote:
> I updated the source of a package of mine last night. The upstream is
> on Github, and I use the %forgemeta macro for an easy spec file. When I
> tried to run "fedpkg build" though, it failed - the build system
> rejected the build because it was expecting an SRPM with a release
> string including 20230507, but instead got one with 20230506.
Could it be that you built the package over midnight UTC, so the SRPM was
still built with 20230506, but when the build happened, it was already
20230507?
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
