Hopefully the correct list, if not apologies. Just updated a package I am newly maintaining, commit diff here: https://src.fedoraproject.org/rpms/keylime/c/563905a7b29096c0fecba1d4279e... When I perform 'fedpkg mockbuild' everything passes, yet 'fedpkg build' results in a build failure from not being able to find the tarball: https://kojipkgs.fedoraproject.org//work/tasks/1266/41421266/build.log

I have verified the URL: https://github.com/keylime/keylime/archive/%{version}.tar.gz > https://github.com/keylime/keylime/archive/5.5.0.tar.gz This resolves as expected. Does anyone have any ideas why this could be (hopefully not something to dumb from my side)? Thanks, Luke _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

It seems you accidentally uploaded the source RPM instead of the tarball. Simply run fedpkg new-sources on the correct file and push the new sources file. The build should then work.

On Fri, Feb 07, 2020 at 01:46:26PM -0700, Ken Dreyer wrote: > I'm not sure where to report such an RFE. Is > https://github.com/release-engineering/dist-git right? yep. Exactly the right place.

On 07. 02. 20 11:20, Luke Hinds wrote: > When I perform 'fedpkg mockbuild' everything passes, yet 'fedpkg build' results > in a build failure from not being able to find the tarball... Hello Luke. Others have already identified the cause, so let me just share a tip about how to debug such issue in the first place. 'fedpkg mockbuild' sees all files in the current directory, it doesn't really let you know if what you have is not what Koji would have. Whether it is local changes, unpushed files, or sources not uploaded to the lookaside cache like in this case. In order to approximate more Koji-like behavior, it is always good idea to clone the package to a different location on disk and try to attempt the build from a clean working directory. (Alternatively, clean the current directory properly, but that can be tricky sometimes, as it requires several different ways of cleaning.) Hope that helps in the future. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok