On Tuesday, June 30, 2020 8:46:10 PM CEST PGNet Dev wrote:
I'm building a pkg on COPR.
It uses forgemeta/scm (from git) for a source.
On build exec, it fails
sh: git: command not found
sh: git: command not found
sh: git: command not found
sh: git: command not found
...
( details ->
https://pastebin.com/vUCVVHQq , line #1806 )
Note, the spec _does_ have "BuildRequires: git".
It appears this^ may have to do with forgemeta needing git earlier? Note that
foregemeta source pulls, subsequent to the error, fail ...
Error output like that is usually "a bug" in macro implementation:
https://github.com/rpm-software-management/rpm/issues/424
Usually those macros are no-ops at SRPM build time, so you can ignore these
errors.
As long as the error output really is innocent.
This build failure seems to be described by the error:
error: You need to define %{version1}, or %{tag1} before the macro invocation !
error: lua script failed: /usr/lib/rpm//lua/fedora/srpm/forge.lua:165: error expanding
macro
But I'm not an expert on %forgementa macros (it's pretty new thing). I'd
suggest you to contact Nicolas Mailhot on fedora devel list.
Does COPR need an earlier preload of 'git' for forgemeta SCM
use by builds?
Copr rebuilds srpm first, from copr dist-git - in limited buildchroot.
If that _is_ the case, where/how does one add a 'early' git
req't for COPR
builds?
Probably. Note that it would be better to not remove the build next time
so we could experiment and try to reproduce the build.
Pavel
_______________________________________________
copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.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.fedorahosted.org/archives/list/copr-devel@lists.fedorahoste...