nim added a new comment to an issue you are following: `` You can do all of this today in Fedora without specific Koji changes or specific client tooling. All you need is an upstream hosted on GitHub or GitLab. Or pretty much every modern source hosting service except pagure because of: https://pagure.io/pagure/issue/861
The required macros are all merged in redhat-rpm-config, the last missing mile is documentation and it’s waiting merging here https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/51
If you control the upstream you are packaging it’s a huge productivity enabler 1. do all the changes you want in the upstream repo branch or in a downstream fork 2. (optionally) tag the state you think will work 3. bump the commit id or tag or version in the spec (no other change needed) 4. spectool 5. build and test
(3/4/5 can be done on another vm/system with different security measures, they do not require write access to the upstream repo)
If the result does not work as expected, commit fixes/move the tag and repeat.
When it all works as expected tag as official upstream release or PR your fork.
This is pretty much the same workflow as creating fake upstream archives to test changes, except it’s all tracked cleanly in SCM and is miles ahead usability-wise.
``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7498