hi,
I've got a local .spec file (working on an nginx build) that's using %forgemeta
macros with '%undefine _disable_source_fetch'.
Local rpmbuild & mock builds for fedora-32-x86_64 work as expected -- sources
are auto-pulled from upstream scm as intended.
The created RPMs seem healthy -- from both rpmbuild & mock builds -- & they're
locally installed without error, and the apps launch/exec.
On submit of the known-to-work-locally .spec file to an my COPR account,
copr-cli build <proj> <spec>
the build quickly fails, not finding the retrieved/tar.gz'd source: "No such
file or directory".
_Does_ automated source_fetch function in COPR using '%undefine
_disable_source_fetch' in the spec?
Or is there different/additional config needed?
Looking at the failed-build log,
https://download.copr.fedorainfracloud.org/results/pgfed/nginx-mainline/srpm-builds/01502815/builder-live.log.gz
the build dies at
stderr: error: Bad source:
/tmp/copr-rpmbuild-s7uo_x65/nginx-release-1.19.0.tar.gz: No such file or
directory
Failed to execute command.
Again -- works without error on local builds with the same .spec file.
I notice the %forgemeta %dist tag is set as
dist: .gitrelease.1.19.0.fc31
-- note the "fc31", even though the repo settings at
https://copr.fedorainfracloud.org/coprs/pgfed/nginx-mainline/edit/
explicitly set/select the fc32
fedora-32-x86_64
chroot.
Is %forgemeta source retrieval and subsequent tarball creation & population
into BUILDROOT on COPR known to work?
If so, I'm obviously missing _something_.
Any suggestions/hints would be appreciated; the "No such file or directory"
isn't particularly informative to me ...
_______________________________________________
copr-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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.fedorahosted.org/archives/list/[email protected]
