Your message dated Fri, 29 Jan 2016 13:33:57 -0800
with message-id <[email protected]>
and subject line Re: [regression 2.5.0->2.5.1] git pull fails: "git
upload-pack: git-pack-objects died with error"
has caused the Debian Bug report #798602,
regarding git: git pull regression with 2.5.1: "git upload-pack:
git-pack-objects died with error"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
798602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798602
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
Version: 1:2.6.2-1
Hi Axel,
Axel Beckert wrote:
> Jonathan Nieder wrote:
>> There is a change on the "next" branch:
>>
>> aab40438 git_connect: clear GIT_* environment for ssh, 2015-09-04
>>
>> It filters out the following variables:
[...]
>> I think that should help. It will probably land in 2.7.0, […]
>
> Did it land in 2.7.0 in the end? If so that bug could be closed either
> with version 1:2.7.0~rc3-1 or with version 1:2.7.0-1.
It landed in 2.6.2 (v2.6.2~19^2~1). Thanks for the reminder.
Sincerely,
Jonathan
--- End Message ---
