DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 44S1UVJb997067
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=uNG1JxEO
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B985F384AB6D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1716859829;
	bh=sLYlhTy4PGBAI9Nhd8JjYqDfJYnoIrVDFh1SVt4bQSM=;
	h=References:In-Reply-To:Date:Subject:To:Cc:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 From:Reply-To:From;
	b=uNG1JxEOKMhApfRa6vFUqqj6p+h/CT7PqtTr2AC2ap4/g46JeSk9Uw/C6zeWKzYxx
	 2wdIRdtbT7NzNa6ZO/Ac5C/47F543EXw5xwb8utMtxDCFSYpe5Hi9+XcdFxD/erolu
	 HaA7wUlON41c6jbneSwr4PJaI8YgVeyW39m3DjyE=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org DCAE43870C34
ARC-Filter: OpenARC Filter v1.0.0 sourceware.org DCAE43870C34
ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1716859792; cv=none;
 b=u+3MizQJdECgV5VDl2QI18ZNUJmKt/JQQXEubGZTsoCBjk9ZTrZxao6OhZDgNTWbSuWyRt/3PLFf6iOqFLDeQ8aF4iCpliO2ostPcDf5v7YSgygA9lD88Ug5LVu4dajPI3VWPlMcqmA4GxFVPBxalbg3OwgA8YtGTCpKL3fGuMA=
ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key;
 t=1716859792; c=relaxed/simple;
 bh=YhdQGqsPvYJuzwEDfT7X73LO/0wdSpyAEvkIYXSyF7s=;
 h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To;
 b=VKdYWfFek8y0XqEnHKTIWvFE5/yMlHLdX+JxZxAtW715xNcEElyEoWVQoWDpdh4Ws93Q662CVX1QcrkJBJaViQm6T9yRDHrJTjEW878//2jyl9IobyFNDSy+SVS48hKgeR1E6RisJG769yFXQxOfhO0vybCr5TcilPWguYordu8=
ARC-Authentication-Results: i=1; server2.sourceware.org
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20230601; t=1716859789; x=1717464589;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
 :reply-to;
 bh=QDn8Ny8vbI32XQATKMgsVKB9zX8sgAkFexldbY8ilMI=;
 b=b44fuaEElVz/XkV22MR78ZyYENRrawRDUDc3Nfvp8lv2a1YCKDBBl9TK5kWk1SEkaQ
 S+CV0FZW6RcxHdqzR1W/SacWYzVec7rQ99YiTfL9hOSU6jCFwDK3NKAkiJmYtLH+1g5H
 6lL36WLoCV3gO3PkC+1DxFatUOs4K8Xl5yePVFIgS9fIgkvobKz1mvBLjYTG+qsO+fog
 oDcOoUbxJYjdeSYe0QnbkbqZ+XSIinQs93PMDLp1d3xLA0u+UghhzPj2D9zRovuP7KQy
 3D1q5MBHqmPlHcV0ca9zsCvyQnPbRtMa669VFK1VFRnvYV+II34+lqEno4WrooMHGMqe
 W4Vg==
X-Gm-Message-State: AOJu0Yys4/V6jxGbWPv08hwRUCuXBzaKwg5zmQwOD6pv3xMsEdqKR39d
 97QrF3WAyTHhT8SS7DhoSGUE0sbZqNNOe2JAugkZZf4v+iB/RGkeJHULde5S0PKl2jvVfjoBtzk
 b8AFAJJgnKNzww9vfrrnL+t4l6aGJPc7spB0=
X-Google-Smtp-Source: AGHT+IHZBZF51XITCiLGabjOyRPnRVPkrKisQFmow9r1U1WflG72qxEVvX1bfKwLFNmr2ValGkK6YFl48QE1+75AotI=
X-Received: by 2002:a17:90b:190e:b0:2b1:e314:a5e6 with SMTP id
 98e67ed59e1d1-2bf82fbbc38mr6765060a91.7.1716859788797; Mon, 27 May 2024
 18:29:48 -0700 (PDT)
MIME-Version: 1.0
References: <CAJtSMgvg+2z1y46J5k3FKxO=YZ9gzOiVzUY5qEgHZQW9Bp=3cg AT mail DOT gmail DOT com>
 <CA+kUOakzh4egc=t27+c62F_hGUMNgecvzay9Af55hQC1Zd=VFQ AT mail DOT gmail DOT com>
 <CAJtSMgv6sDwUKCrMVLyPeRCwH9stLFRb6a6+ABor0u40n95ong AT mail DOT gmail DOT com>
 <CA+kUOamgK94wGdfugDp+gRSxJfozEenyXcmB2cewJo1BxTthzg AT mail DOT gmail DOT com>
In-Reply-To: <CA+kUOamgK94wGdfugDp+gRSxJfozEenyXcmB2cewJo1BxTthzg@mail.gmail.com>
Date: Mon, 27 May 2024 18:29:37 -0700
Message-ID: <CAJtSMgvg=oOdnYqZD1WRLDE23tnvmxXzGYp1q4g3t2XsXQfwBw@mail.gmail.com>
Subject: Re: new git update fails with fatal: fetch-pack: invalid index-pack
 output
To: Adam Dinwoodie <adam AT dinwoodie DOT org>
Cc: cygwin AT cygwin DOT com
X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE,
 RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.30
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: David Dyck via Cygwin <cygwin AT cygwin DOT com>
Reply-To: David Dyck <david DOT dyck AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 44S1UVJb997067

Thank you for your ideas!

I have made no changes but can't reproduce the issue today
both with a very short path of /usr/bin and the original path
I tried with VPN off or on
I would be happy to try a few other experiments - but I don't even need the
workaround of reverting to an older git


$ which git
/usr/bin/git

$ git --version
git version 2.45.1

OPATH="$PATH"
PATH="/usr/bin"
git clone -v https://github.com/lxml/lxml.git

mv lxml lxml-
PATH="$OPATH"
git clone -v https://github.com/lxml/lxml.git

while rm -rf lxml && time git clone -v https://github.com/lxml/lxml.git  ;
do date ; done

at the moment the above loop runs hundreds of times without errors

On Mon, May 27, 2024 at 1:31 PM Adam Dinwoodie <adam AT dinwoodie DOT org> wrote:

>
>
> I've just set up a test sandbox with the same set of Cygwin
> applications installed, and I'm still not able to replicate this
> failure, which is going to make it difficult to work out what's going
> wrong for you!
>
> I note your Cygwin PATH has several entries before /bin, including a
> ~/bin that apparently contains a perl executable; can you see if you
> can reproduce the problem with a clean PATH?
>
> In any case, I'm having to conclude the issue is something odd about
> your environment that doesn't seem to be affecting most people.
> Working out what's going wrong will probably require isolating what
> difference is relevant here. I think there's two obvious routes to
> doing that: you can work out what's odd about your environment (maybe
> use Windows Sandbox, given you're running Windows Enterprise? I've
> attached a .wsb file that should give you a starting point for setting
> up test environments, based on your cygcheck.out), or you can work out
> what's changed in Git between 2.42.0 and 2.45.1, which will probably
> mean building and bisecting Git yourself; once we know what change is
> the culprit, that'll make it much easier to work out what's going
> wrong.
>
> If it'd be useful, I can provide some test builds of Git to help
> narrow down where the problem is, but if you can do the builds
> yourself, that'll be a lot quicker than trying to do a binary chop by
> email…
>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple