nim added a new comment to an issue you are following: `` You can get 99% of the convenience without the lack of auditability just by using the existing forge fedora macros.
You declare your forge url in the specfile. You declare the target tag version or commit. You do a `spectool -g` followed by a `rpm -bs` and you get a src.rpm that can be used in all our tools (mock, copr and koji), and uploaded to become the Fedora golden source.
And then it does not matter if upstream reworks its scm or rehosts somewhere else or disappears, because the tarball has been generated at packaging time, and has been checked at packaging time, and it’s no better or worse than to rely on a traditional tarball that could be changed upstream after the Fedora download.
You can even test pre-releases with the spec pointing to commits ids on a feature branch in in your own private pagure.io forked repo, then get the branch merged and tagged in the master repo once the tests are done, with the same spec, replacing only the forked repo url and tested commit id with the master repo url and official version tag once the whole thing is done.
You'll spend more time waiting on pagure.io than changing lines in the spec.
``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7498