Control: severity -1 minor Hi,
Axel Beckert wrote: > 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 My coworker (who ran into this issue on MacOS X) finally found what triggers this issue. It's the following setting in our both's ~/.ssh/config: SendEnv TERM GIT_* Intention of this is to forward variables like GIT_EDITOR, GIT_COMMITTER_NAME, GIT_COMMITTER_EMAIL, GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL via SSH. Unfortunately git since 2.5.1 additionally seems to set GIT_WORK_TREE -- which gets forwarded that way, too. The fix is to change the according line in ~/.ssh/config to SendEnv TERM GIT_EDITOR GIT_COMMITTER_* GIT_AUTHOR_* which is more clumsy, but does the job. Feel free to close this bug report if you consider that a pure configuration issue. I'm nevertheless still surprised about such a change in a micro release -- which IMHO (and in http://semver.org/'s opinion) only should be a fully backwards-compatible bug fix release. Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
