Piere (a.k.a Pingou), Nils and me worked on Rpmautospec [1] to solve this problem few months ago. It is a koji plugin as well as CLI tool that makes bumping the release field and generating changelog problem of Koji, instead of package-maintainer. Currently it sits deployed in staging koji, so you can give it a test-drive :-)
We hope we can return to it later this year, to have it deployed in prod koji. [1] https://docs.pagure.org/Fedora-Infra.rpmautospec/principle.html On Mon, Jul 6, 2020 at 8:22 AM Florian Weimer <fwei...@redhat.com> wrote: > * Björn Persson: > > > The macro could be defined like this for example: > > > > %buildtag .%(date +%%s) > > Using time for synchronization is always a bit iffy. > > > It would be used in each spec like this: > > > > Release: 1%{?dist}%{?buildtag} > > We could put the Koji task ID directly into the %dist tag. We know that > this works in principle. If we are worried that the number gets too > large, we could subtract the current task ID at the time the fcNN part > of the %dist tag changes. > > The %dist tag is not recorded in the changelog by most packages, so the > changelog does not need changing. > > Thanks, > Florian > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org >
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
