(i'd been discussing this issue with praiskup @ copr-devel/buildsys; he
suggested that I bring it here ...)
This spec
https://download.copr.fedorainfracloud.org/results/pgfed/nginx-mainline/fedora-32-x86_64/01516680-nginx/nginx.spec
which uses forgemeta to pull multiple SCM sources, and uses some git/bash
scripting in %defines,
builds locally, on F32, via rpmbuild or mock build, from spec or srpm, with NO
error. resulting rpms are installable, usable & pass testing.
submitting the _same_ spec to COPR for online build FAILS @, supposedly,
similar Mock build
Here's a diff
https://www.diffchecker.com/izjQYkUF
comparing the log output of
SUCCESSFUL LOCAL BUILD
mock --buildsrpm --spec=~/rpmbuild/SPECS/nginx.spec
--sources=~/rpmbuild/SOURCES
cat build.log
and
FAILED COPR BUILD
copr-cli build nginx-mainline ~/rpmbuild/SPECS/nginx.spec
https://download.copr.fedorainfracloud.org/results/pgfed/nginx-mainline/fedora-32-x86_64/01516674-nginx/builder-live.log.gz
The goal is to have the same spec generate the same Mock build, regardless of
environment.
Why does the COPR build's Mock build stage fail?
IIUC, mock builds _should_ be portable between mock envs, at least for the same
chroot.
Do I need additional prep of the spec prior to submit? Something in my
foregemeta/scm usage that's env-dependent? Something else I've missed?
Or is there an issue with the Mock build env @ COPR?
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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
