Package: git Severity: important Version: 1:2.5.1-1 Tags: upstream Since git 2.5.1 pulling from some repos (being hosted on a Debian 8 Jessie host) no more works:
~/foo/fookb → git remote -v origin fookb@…:fookb.git (fetch) origin fookb@…:fookb.git (push) ~/foo/fookb → git pull remote: fatal: Could not switch to '/home/abe/foo': No such file or directory error: git upload-pack: git-pack-objects died with error. fatal: git upload-pack: aborting due to possible repository corruption on the remote side. remote: aborting due to possible repository corruption on the remote side. fatal: protocol error: bad pack header "git clone" from the same repository no more works either.yo As you can see, I'm not logging in with my local user but with a specific user for that repository, i.e. I don't have a normal user account named "abe" there and hence also no /home/abe exists remotely. This worked before and a friend of mine was able to reproduce the very same issue with Git 2.5.1 on a Mac while it worked with Git 2.5.0 for him. So this seems to be an upstream regression in 2.5.1. We currently suspect this upstream change (cited from /usr/share/doc/git/RelNotes/2.5.1.txt) to be the cause for this issue: * "git pull" in recent releases of Git has a regression in the code that allows custom path to the --upload-pack=<program>. This has been corrected.
