You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PackingType of packed-Refs not understood: '# pack-refs with: peeled fully-peeled sorted' #687
File "/usr/lib/python2.7/dist-packages/git/repo/base.py", line 335, in tags
return TagReference.list_items(self)
File "/usr/lib/python2.7/dist-packages/git/util.py", line 932, in list_items
out_list.extend(cls.iter_items(repo, *args, **kwargs))
File "/usr/lib/python2.7/dist-packages/git/refs/symbolic.py", line 613, in _iter_items
for sha, rela_path in cls._iter_packed_refs(repo): # @UnusedVariable
File "/usr/lib/python2.7/dist-packages/git/refs/symbolic.py", line 97, in _iter_packed_refs
raise TypeError("PackingType of packed-Refs not understood: %r" % line)
I guess the "sorted" token can be safely ignored; _iter_packed_refs() could probably be somewhat improved by adding a whitelist of supported tokens, the current code looks a bit fragile (but then, I don't know what the syntax and semantics for the packed-refs header is).
👋 We're hitting the same issue now that brew is upgrading our users' git to 2.15. Any way we could get a 2.1.8 release out with this patch?
Reacted by Damien Robertson, Tim Blechmann, Chris Fournier, Mykola Rybak, Chris Watson, Benjamin Esham, Rob Cowie, Nick Klauer, samhsuqld, Ben Eshed and 20 more
branches = repo.branches
File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/git/repo/base.py", line 267, in heads
return Head.list_items(self)
File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/git/util.py", line 942, in list_items
out_list.extend(cls.iter_items(repo, *args, **kwargs))
File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/git/refs/symbolic.py", line 609, in _iter_items
for sha, rela_path in cls._iter_packed_refs(repo): # @UnusedVariable
File "/home/travis/virtualenv/python2.7.13/lib/python2.7/site-packages/git/refs/symbolic.py", line 100, in _iter_packed_refs
raise TypeError("PackingType of packed-Refs not understood: %r" % line)
TypeError: PackingType of packed-Refs not understood: '# pack-refs with: peeled fully-peeled sorted'
Can I request a release with this patch included please? Git 2.15 is the stable release as of Oct 30th.
Reacted by César Izurieta, Matthew Robinson, Jonathan Sibley, harbesc, samhsuqld, Elliot Wright, Lucas Mezêncio, Oleksandr Podze, Florent Audebert, nuzz and 16 more
Is there an ETA on when you'll package a v2.1.8 release that includes this fix?
Reacted by Ben Tomasik, Jarrod Moore, Marcos Benatti Lauer, Jeroen van Erp, courteouselk, Konrad Materka, Shaina Johl, Chris Watson, samhsuqld, Roy Van Ginneken and 16 more
Reacted by Paolo D., yachi, small2kuo and Eli Wang
Rather than closing in preparation for the release, would you consider re-opening and then closing once the release is available? That way those of us who subscribe to notifications on this issue will be alerted to the availability of the new release.
Reacted by Nick Klauer, Greg A. Woods and Russell McClellan
I hit this issue and have limited control of getting the upgrade -- if anyone is in a similar situation you can workaround it by calling repo.git.tag().
Activity
bjb commentedon Oct 13, 2017
See pull request #689. i had the same problem after upgrading git.
JasonMWhite commentedon Nov 1, 2017
👋 We're hitting the same issue now that brew is upgrading our users' git to 2.15. Any way we could get a 2.1.8 release out with this patch?
HariSekhon commentedon Nov 7, 2017
Same problem:
See full build log here:
https://travis-ci.org/HariSekhon/pytools/builds/298554130#L6405
JasonMWhite commentedon Nov 7, 2017
The fix has been merged to master, the next time a release is cut we should be all set.
paulbovbel commentedon Nov 7, 2017
Can I request a release with this patch included please? Git 2.15 is the stable release as of Oct 30th.
nuzz commentedon Nov 13, 2017
Is there an ETA on when you'll package a v2.1.8 release that includes this fix?
damian-lewkowicz commentedon Nov 29, 2017
Any news?
Workaround - install unreleased version :)
igor-raits commentedon Nov 29, 2017
Or install packaged version in your $distro which has patch :P
hugovk commentedon Dec 4, 2017
See #704 about a new release.
Byron commentedon Dec 11, 2017
I am closing this issue in preparation for the next release, which contains the fix. I am sorry for having let you wait for so long!
truthdoug commentedon Dec 11, 2017
Rather than closing in preparation for the release, would you consider re-opening and then closing once the release is available? That way those of us who subscribe to notifications on this issue will be alerted to the availability of the new release.
JasonMWhite commentedon Dec 11, 2017
Thanks @Byron ! I appreciate it :)
Byron commentedon Dec 11, 2017
@truthdoug I totally agree, and fortunately the waiting is over now: https://pypi.python.org/pypi/GitPython
Bump required GitPython (#68)
Bump GitPython to 2.1.8 to include fix for gitpython-developers/GitPy…
Bump GitPython to 2.1.8 to include fix for gitpython-developers/GitPy…
Bump GitPython to 2.1.8
Bump GitPython to 2.1.8
Bump GitPython to 2.1.8
Bump GitPython to 2.1.8
pmb311 commentedon Oct 2, 2018
I hit this issue and have limited control of getting the upgrade -- if anyone is in a similar situation you can workaround it by calling repo.git.tag().
Byron commentedon Oct 14, 2018
@pmb311 I believe you can always monkey-patch the code, based on the fix that has been released by now. Do you think that will work?
dockerfile: stop using python3-git for Quibble Stretch