ngompa added a new comment to an issue you are following: ``
But in the common case, the dist-git repo will point to the upstream repo and commit, and a user can go to that repo and view the full history of the source that was built into the srpm. Isn't that a better experience than what we have today, when that chain of custody always ends at the tarball in our lookaside cache?
No, because that repo isn't guaranteed to be around. As I said earlier, I think that if we wanted to allow this, we'd need to go full-on repo forking to make it work. And that also adds some complexity because repositories are different types, different features in use, and so on. In the space of purely Git repos, Pagure does not yet have all the necessary functionality to mirror every single Git repo, principally because it lacks support for Git LFS and Git-Annex.
That's not even getting into the mess related to supporting Mercurial, Bazaar, SVN, and CVS repositories. We'd need some kind of process to handle those in a sensible manner too. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7498