Packages where spec file name and git repo name don't match break lookaside cache urls in fedpkg. For example, a package called 'glibmm24' has spec file 'glibmm.spec'. Running 'fedpkg prep' results in: {{{ $ fedpkg prep % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Could not prep: Command '['curl', '-H', 'Pragma:', '-O', '-R', '-S', '--fail', '--show-error', 'http://pkgs.fedoraproject.org/repo/pkgs/glibmm/glibmm-2.24.1.tar.bz2 /3f16e63871257ee037ad39a3e5f01922/glibmm-2.24.1.tar.bz2']' returned non-zero exit status 22 }}}
Koji buildSRPMFromSCM fails in a similar way. As we discussed on IRC, I'm going to fix this particular package up by renaming the spec file. However, even though there is a Fedora packaging guideline requirement that spec file name needs to match base package name, fedpkg should probably not make such assumptions.
suggested patch to solve this ticket 0001-patch-suggestion-for-solve-Ticket-75.patch
Sorry, this patch is incomplete, because it seems to work only, if you create your repository with fedpkg clone .
Unfortunately, It's seem there is no function to remove an accidently attached file
I think the plan here is to detect when the spec file doesn't match the repo name and complain to the user to fix it. It has been a requirement in Fedora that these match up for a while now.
Actually I did fix this so that the spec can mis-match. We'll just figure out the name of the package from within the specfile. If /that/ mismatches, well then I give up :)