Historically we used 'pyrpkg' (alternative to fedpkg import) for importing uploaded srpms (or srpms pointed to by url). Now, copr reimplements this itself (extracts that by rpm2cpio, reading the list with cpio, removing old files from distgit, etc., etc..). This is architectonic issue and maintenance disaster; please implement the functionality in pyrpkg so we don't duplicate the efforts or (if you plan to experiment in Fedora Copr) please provide an option so I can have limited feature set (but using the proper tools).
That would mean we would again need to build srpms on copr-dist-git or have two ways of importing - one directly from downstream or upstream repo and another from a srpm. The current approach has an advantage of utilizing only one way of doing things. If the functionality we need was present in pyrpkg, then we would be able to use it. It is not however and won't be in near feature. This is not a bug, nor a feature request, however. It is just 'how-to' do something.
(In reply to clime from comment #1) > That would mean we would again need to build srpms on copr-dist-git Why? First the builders still provide srpms, which are imported on dist-git side. This bug report is only about this "import" issue. Second misusing srpm archive for transport between builder <-> distgit is another issue -- but replacing "srpm import" (on dist-git side) by "tarball" import or by plain "rsync" from backend (or even builder!) would also fix this issue an elegant way... > or have two ways of importing - one directly from downstream or upstream > repo and another from a srpm. This is natural and good because you actually don't have to implement srpm import at all when it is already done by pyrpkg. > The current approach has an advantage of utilizing only > one way of doing things. If the functionality we need was present in pyrpkg, > then we would be able to use it. It is not however and won't be in near > feature. Proposal needed I guess! That's what should have been already done :-) > This is not a bug, nor a feature request, however. It is just 'how-to' do > something. Duplicating efforts is bug in fedora ecosystem. I just opened against the culprit component. Feel free to reopen.