Once upon a time, Kevin Kofler <kevin.kofler@xxxxxxxxx> said: > 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? It wasn't that, I tried it several times. Also, the forge macro is using the timestamp of the source file, not the wall clock (so the system clock being wrong wouldn't have caused it either). -- Chris Adams <linux@xxxxxxxxxxx> _______________________________________________ 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
