Repository navigation
PackingType of packed-Refs not understood: '# pack-refs with: peeled fully-peeled sorted' #687
Description
Activity
See pull request #689. i had the same problem after upgrading git.
👋 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 moreSame problem:
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'See full build log here:
https://travis-ci.org/HariSekhon/pytools/builds/298554130#L6405
The fix has been merged to master, the next time a release is cut we should be all set.
Reacted by Hari Sekhon, Ryan Fisher, Christopher Bloom, Ben Tomasik and Derek LinCan 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 moreIs 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 moreReacted by Paolo D., yachi, small2kuo and Eli WangAny news?
Workaround - install unreleased version :)
pip install -U git+http://github.com/gitpython-developers/GitPython.git
Reacted by Andreu Belmonte, Dmitrii Shamrikov and Ryan FisherReacted by yachiOr install packaged version in your $distro which has patch :P
See #704 about a new release.
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!
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 McClellanThanks @Byron ! I appreciate it :)
@truthdoug I totally agree, and fortunately the waiting is over now: https://pypi.python.org/pypi/GitPython
Reacted by Hugo van Kemenade, clayton craft and Doug HarrisReacted by Hugo van Kemenade, Markus Siemens, John Kurkowski, clayton craft, Charlie McBride and Foaly- added a commit that references this issue
on Dec 11, 2017 - added 4 commits that reference this issue
on Feb 9, 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().
@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?
- added a commit that references this issue
on Aug 18, 2020
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).