On Thursday, June 25, 2020 4:41:06 AM CEST PGNet Dev wrote: > _Does_ automated source_fetch function in COPR using '%undefine > _disable_source_fetch' in the spec? Or is there different/additional > config needed?
Yes, but you need to do `%define _disable_source_fetch 0` instead. Undefining the macro for some reason breaks rpmbuild. Well, copr code already does that for you (so you don't have to actually touch the _disable_source_fetch macro at all). > 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 ... Not even to me. I had to look at the code to see what is happening: 1. we create rpmmacros file with some macros: https://pagure.io/copr/copr/blob/58af9ef7cf4b4eccd829b17a2de2afd043b95ce0/f/rpmbuild/copr_rpmbuild/providers/base.py#_26-32 2. then we do https://pagure.io/copr/copr/blob/58af9ef7cf4b4eccd829b17a2de2afd043b95ce0/f/rpmbuild/copr_rpmbuild/providers/spec.py#_25-28 First, this is wrong. We shouldn't use 'rpkg' on host for this task, perhaps we should just use 'mock --buildsrpm --enable-network' here. Pavel _______________________________________________ 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]
