fweimer added a new comment to an issue you are following: ``
@fweimer can you walk us through how your workflow would look if we had this enabled? ie, how it would be better?
I make a commit to a Fedora repository with a cherry-picked upstream commit (using `git cherry-pick`, perhaps with some commit message adjustments for bug references, but no separate tools and no additional file changes). I push and run `fedpkg build`, and the infrastructure does the rest.
I think the reproducibility is minor but still there (in the case you build something, upstream dies or changes hashes or does something wacky) you can't just rebuild the src.rpm right? You would need to modify it to use the exact source that was used on that build? Or no?
Given that we keep the source RPM, I think rebuilding is not critical from a reproducibility perspective.
The availability issue is also there for me: If remote is down, build fails right?
Yes, but I would expect the repository to live on `src.fedoraproject.org`, so that wouldn't be a change from today.
I suppose it would be easy enough to switch back to a uploaded tar.gz in case remote is down and we urgently need to get something built?
I don't think this would be necessary if the Git repository is hosted by the right Fedora infrastructure. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7498