When using %autorelease -s %{date}git%{shortcommit}
%autorelease -s %{date}git%{shortcommit}
I get the wrong src.rpm filename generated, but the changelog seems correct:
cachelib on rawhide [⇡] ❯ fedpkg srpm && rpm -qp --changelog ./*.src.rpm | head -n 20 Not downloading already downloaded CacheLib-c4904ef2524f396eb432392f8308a69dda926bd8.tar.gz setting SOURCE_DATE_EPOCH=1640736000 Wrote: /home/michel/src/fedora/pkgs-meta/folly/cachelib/cachelib-16-2.20211220gitc4904 ef.20211220gitc4904ef.fc36.src.rpm * Wed Dec 29 2021 Michel Alexandre Salim <salimma@fedoraproject.org> 16-2.20211220gitc 4904ef - Update to snapshot from 2021.12.20 * Wed Dec 29 2021 Michel Alexandre Salim <salimma@fedoraproject.org> 16-1 - Initial Fedora package
I'm temporarily reverting to using -e which seems to generate the correct src.rpm and changelog entries.
-e
I think this is because your are using forge macros, Forge macros compute the snapinfo and put it in the dist tag, so the dist tag of the autorelease also contains snapinfo.
Forge macros are not really compatible with rpmautospec and its maintainer is MIA.
I believe you could disable the forge macro snapinfo generation with:
%global distprefix %{nil}
I think this is because your are using forge macros, Forge macros compute the snapinfo and put it in the dist tag, so the dist tag of the autorelease also contains snapinfo. Forge macros are not really compatible with rpmautospec and its maintainer is MIA. I believe you could disable the forge macro snapinfo generation with: %global distprefix %{nil}
I believe you could disable the forge macro snapinfo generation with: %global distprefix %{nil}
thanks, that works. As a bonus this means I could actually use the new-style versioning guideline too!
Metadata Update from @salimma: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.