Le jeudi 02 juillet 2020 à 18:00 -0700, PGNet Dev a écrit : Hi, As usual for those things the reason is dead stupid (so stupid the human brain refuses to see it) > submitting the _same_ spec to COPR for online build FAILS @, > supposedly, similar Mock build > > Here's a diff > > https://www.diffchecker.com/izjQYkUF > The fail log is full of sh: git: command not found sh: git: command not found sh: git: command not found sh: git: command not found sh: git: command not found sh: git: command not found sh: git: command not found sh: git: command not found sh: git: command not found You added some processing that depends on the git command (that forgemeta does not use) but forgot to BuildRequire the package providing that command. As stated before forgemeta does not depend on the git (or hg, or svn, or…) command, it’s a pure URL munger, so it won’t pull in your scm of choice in the buildroot. Presumably your workflow is so git oriented your local setup always has git installed. Regards, -- Nicolas Mailhot _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
