With better formatting:

{{{
DEBUG util.py:281: Executing command: ['fedpkg', 'sources']
DEBUG util.py:247: Traceback (most recent call last):
DEBUG util.py:247: File "/usr/bin/fedpkg", line 1466, in <module>
DEBUG util.py:247: import pyfedpkg
DEBUG util.py:247: File "/usr/lib/python2.7/site-packages/pyfedpkg/init.py", line 26, in <module>
DEBUG util.py:247: import git
DEBUG util.py:247: File "/usr/lib/python2.7/site-packages/git/init.py", line 28, in <module>
DEBUG util.py:247: _init_externals()
DEBUG util.py:247: File "/usr/lib/python2.7/site-packages/git/init.py", line 22, in _init_externals
DEBUG util.py:247: raise ImportError("'gitdb' could not be found in your PYTHONPATH")
DEBUG util.py:247: ImportError: 'gitdb' could not be found in your PYTHONPATH
DEBUG util.py:320: Child returncode was: 1
}}}

I've untagged GitPython. As soon as the buildroot regenerates it should start working again.

I know we don't want to untag after something has shipped out in a rawhide compose, but we HAVE to anyhow, since the buildroot is broken and we can't build the fixed package. ;)

I looked at the issue some, but python-gitdb is being correctly pulled in, so I am not sure why it can't be correctly imported. Adding package maintainer here to comment.

if anyone wants to look at it, my rawhide machine has the affected GitPython installed and 'fedpkg sources' in a checkout shows the issue.

Oops. This is my fault for the GitPython build. It worked here in very limited testing or so I thought. I'm going to be traveling tomorrow and in heavy meetings all week, so probably best to leave that GitPython build untagged until I can sort it out with local testing.

Again sorry for the breakage, I had forgotten it would be used to get sources and thus a very critical part of the build environment.

should be fixed now.