#10995 Build fails with error running GIT command
Closed: Fixed by frankcrawford. Opened by frankcrawford.

  • Describe the issue
    Attempt to build new EPEL9 candidate for python-importlib-metadata fails with BuildError:
    FAILED: BuildError: Error running GIT command "git reset --hard 4c49c358f2ea81009cb54765c251ff6bee79bc8c", see checkout.log for details

Full log is

Building python-importlib-metadata-4.6.3-2.el9 for epel9-candidate
Created task: 91280187
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=91280187
Watching tasks (this may be safely interrupted)...
91280187 build (epel9-candidate, /rpms/python-importlib-metadata.git:4c49c358f2ea81009cb54765c251ff6bee79bc8c): free
91280187 build (epel9-candidate, /rpms/python-importlib-metadata.git:4c49c358f2ea81009cb54765c251ff6bee79bc8c): free -> FAILED: BuildError: Error running GIT command "git reset --hard 4c49c358f2ea81009cb54765c251ff6bee79bc8c", see checkout.log for details
  0 free  0 open  0 done  1 failed
  91280188 buildSRPMFromSCM (/rpms/python-importlib-metadata.git:4c49c358f2ea81009cb54765c251ff6bee79bc8c): FAILED: BuildError: Error running GIT command "git reset --hard 4c49c358f2ea81009cb54765c251ff6bee79bc8c", see checkout.log for details
91280187 build (epel9-candidate, /rpms/python-importlib-metadata.git:4c49c358f2ea81009cb54765c251ff6bee79bc8c) failed
  • When do you need this? (YYYY/MM/DD)
    ASAP

  • When is this no longer needed or useful? (YYYY/MM/DD)
    N/A

  • If we cannot complete your request, what is the impact?
    Can't add package to EPEL9


How did you initiate the build? That git hash is not in the distgit repository.

I did fedpkg build --scratch on epel9 branch and it fails during the build process https://koji.fedoraproject.org/koji/taskinfo?taskID=91281072

It was originally run with a fedpkg build in my local copy of the epel9 branch.

Anyway, that was the hint I needed, as I deleted my local copy and cloned it again. I found that it didn't have my previous updates, so I don't know what happened to them, but I can now build it again. Looks like my previous push didn't go correctly.

Thanks for your help.

Metadata Update from @frankcrawford:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata