git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Nipunn Koorapati <nipunn1313@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: Partial clone fails with file:/// URI
Date: Thu, 15 Oct 2020 00:41:08 +0100	[thread overview]
Message-ID: <CAN8Z4-V2zb4kLw9wgkWxf+Cs9NdgUu5YHnhtDZm0qiqf4WS+BA@mail.gmail.com> (raw)
In-Reply-To: <20201014172746.GB2044338@nand.local>

I improved the "bad pack header" error message in a patch off of
v2.28.0 (https://github.com/gitgitgadget/git/pull/755)
However, rebasing onto v2.29.0, it seems like the error no longer
occurs during checkout.
Was there some recent improvement? Looking through the changelog, I'm
not finding anything obvious.

It appears that regardless of
git config uploadpack.allowanysha1inwant true

we find `git checkout` succeeds on v2.29.0

There is a test case in the PR above
Also a manual repro:

cd git
git checkout v2.29.0-rc1
make
cd ..
git/git clone --filter=blob:none file://$(pwd)/git a_clone_of_git

Thanks
--Nipunn

On Wed, Oct 14, 2020 at 6:27 PM Taylor Blau <me@ttaylorr.com> wrote:
>
> On Wed, Oct 14, 2020 at 06:04:18PM +0100, Nipunn Koorapati wrote:
> > Hi,
> >
> > I've been building git from source and directly using the executable. Roughly
> > ```
> > cd git
> > make
> > cd ..
> > git/git clone --filter=blob:none file://$(pwd)/git a_clone_of_git
> > ```
> >
> > This is what I was missing:
> > git config uploadpack.allowanysha1inwant true
> >
> > If this is not set, then the checkout fails w/ a
> >
> > fatal: protocol error: bad pack header
> >
> > Perhaps the error message and/or docs could be improved here to
> > something with more detail than "bad pack header"?
> > Not seeing anything to suggest this in the docs
> > https://git-scm.com/docs/partial-clone
>
> Ah. OK; I feel much better knowing what the difference between our two
> setups is. This is a long-standing issue (I remember seeing it when I
> was experimenting with partial clones several releases ago) so I'm glad
> that we _don't_ have to treat this as a regression in 2.29.
>
> > Thanks for the prompt response. Appreciated!
> > --Nipunn
>
> Thanks,
> Taylor

  reply	other threads:[~2020-10-15  2:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 16:38 Partial clone fails with file:/// URI Nipunn Koorapati
2020-10-14 16:56 ` Taylor Blau
2020-10-14 17:04   ` Nipunn Koorapati
2020-10-14 17:27     ` Taylor Blau
2020-10-14 23:41       ` Nipunn Koorapati [this message]
2020-10-15  1:20     ` Jeff King

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=CAN8Z4-V2zb4kLw9wgkWxf+Cs9NdgUu5YHnhtDZm0qiqf4WS+BA@mail.gmail.com \
    --to=nipunn1313@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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).