From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Philipp Eib <philipp.w.eib@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Error in 'git clone' via SSH in v2.33.0 (related to commit ae1a7ee)
Date: Fri, 22 Oct 2021 16:40:02 +0200 [thread overview]
Message-ID: <211022.86mtn1jf5w.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <CAN2Gq0de1tpiLNcQqoZmgAu=kuOXxEmAtziWM7OJtGPGhLneYQ@mail.gmail.com>
On Fri, Oct 22 2021, Philipp Eib wrote:
> Hi,
>
> Using git-for-windows, I noticed that an SSH git clone of an internal
> repo broke for me in git v2.33.0
> The exact error is:
>
> fetch-pack: unexpected disconnect while reading sideband packet/s
> fatal: early EOF
> fatal: fetch-pack: invalid index-pack
>
> Cloning via HTTPS continued to work.
> It was also repository-specific as cloning other repositories from the
> same (Gitlab) instance via SSH was working fine.
>
> Together with the maintainer we traced the problem back to git commit
> ae1a7ee (https://github.com/git/git/commit/ae1a7eefffe60425e6bf6a2065e042ae051cfb6c).
> Reverting this commit and rebuilding fixed the issue within git-for-windows.
> (You can read the full conversation here:
> https://github.com/git-for-windows/git/issues/3444)
>
> Unfortunately I cannot give a reproducible example as the internal
> repository cannot be shared.
> I have also not tested on linux.
This is probably the same issue as discussed in
https://lore.kernel.org/git/YWX7cd5e5q84CDEv@coredump.intra.peff.net/
next prev parent reply other threads:[~2021-10-22 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 14:26 Error in 'git clone' via SSH in v2.33.0 (related to commit ae1a7ee) Philipp Eib
2021-10-22 14:40 ` Ævar Arnfjörð Bjarmason [this message]
2021-10-22 15:29 ` Johannes Schindelin
2021-10-22 19:40 ` Jeff King
2021-10-22 21:26 ` Carlo Arenas
2021-10-23 3:58 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=211022.86mtn1jf5w.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=philipp.w.eib@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).