On Wed, 21 Jun 2023 13:24:53 +0200 Fabio Valentini <decathorpe@xxxxxxxxx> wrote: > On Wed, Jun 21, 2023 at 1:18 PM Dan Horák <dan@xxxxxxxx> wrote: > > > > On Wed, 21 Jun 2023 12:50:13 +0200 > > Sandro <lists@xxxxxxxxxxxxx> wrote: > > > > > On 21-06-2023 10:51, Dan Horák wrote: > > > > Hi, > > > > > > > > I have met a package that uses %autorelease and wanted to add a suffix > > > > to the release for my local test build that doesn't have to be > > > > compliant with the official versioning, but just differentiate interim > > > > builds. It's quite common to append eg. ".rhbz123456" or similar > > > > suffices. It looks to me that the current %autorelease doesn't allow > > > > that per [1]. Did I miss something or should I file a RFE? > > > > > > > > [1] https://docs.pagure.org/fedora-infra.rpmautospec/autorelease.html > > > > > > I think '%autorelease -e rhbz123456' should do what you want. > > > > per the docs it adds the string into the "middle" > > > > I would like to achieve NVR like > > systemd-250.10-2.fc36.rhbz123456 > > > > which you do with > > Release: 2%{?dist}.rhbz123456 > > > > in the classic spec file > > I think you should be able to do something like this: > Release: %{autorelease}.rhbz123456 > (I have not tested this since I'm not at my "work" machine right now). > (Wrapping the %autorelease macro in {} is probably necessary to ensure > the .rhbz123456 is not interpreted as an argument to the macro.) thanks, that does it :-) Wrote: /builddir/build/RPMS/systemd-253.5-3.fc38.rhbz123456.s390x.rpm Dan _______________________________________________ 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
