From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: git@vger.kernel.org, Eric Wong <e@80x24.org>,
Junio C Hamano <gitster@pobox.com>
Cc: Takahiro Akashi <takahiro.akashi@linaro.org>, Wolfgang Denk <wd@denx.de>
Subject: [BUG] Cloning with git HEAD fails for some repositories
Date: Fri, 22 Mar 2019 07:02:41 +0100 [thread overview]
Message-ID: <017964a9-bd75-5e36-0de7-57d4467d6a7e@gmx.de> (raw)
In-Reply-To: <20190322005107.GL9937@linaro.org>
Initial cloning via
git clone http://git.denx.de/u-boot-efi.git
fails with git version 2.21.0.196.g041f5ea1cf
git version 2.1.4 works fine.
Bisection points to this first bad commit:
17966c0a63d25b1cc2dd1e98d30873e643bd581f
http: avoid disconnecting on 404s for loose objects
Please, fix the regression.
$ git clone http://git.denx.de/u-boot-efi.git
Cloning into 'u-boot-efi'...
warning: alternate disabled by http.followRedirects:
http://git.denx.de/u-boot.git/
error: Unable to find a00d15757d7a513e410f15f2f910cb52333361a3 under
http://git.denx.de/u-boot-efi.git
Cannot obtain needed object a00d15757d7a513e410f15f2f910cb52333361a3
error: fetch failed.
$ git clone git://git.denx.de/u-boot-efi.git
Cloning into 'u-boot-efi'...
remote: Counting objects: 602001, done.
remote: Compressing objects: 100% (96111/96111), done.
remote: Total 602001 (delta 498315), reused 600868 (delta 497450)
Receiving objects: 100% (602001/602001), 120.33 MiB | 11.28 MiB/s, done.
Resolving deltas: 100% (498315/498315), done.
$ cd u-boot-efi/
/u-boot-efi$ git remote remove origin
/u-boot-efi$ git remote add origin http://git.denx.de/u-boot-efi.git
/u-boot-efi$ git fetch
From http://git.denx.de/u-boot-efi
* [new branch] efi-2019-04 -> origin/efi-2019-04
* [new branch] efi-2019-07 -> origin/efi-2019-07
* [new branch] master -> origin/master
/u-boot-efi$
Setting
git config --global \
http.http://git.denx.de/u-boot-efi.git.followRedirects true
avoids the warning but does not solve the problem:
$ git clone http://git.denx.de/u-boot-efi.git
Cloning into 'u-boot-efi'...
warning: adding alternate object store: http://git.denx.de/u-boot.git/
error: Unable to find a00d15757d7a513e410f15f2f910cb52333361a3 under
http://git.denx.de/u-boot-efi.git
Cannot obtain needed object a00d15757d7a513e410f15f2f910cb52333361a3
error: fetch failed.
Best regards
Heinrich
next parent reply other threads:[~2019-03-22 6:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7e4a2f1d-2b3a-eb83-d3f1-9ac63d68991b@gmx.de>
[not found] ` <20190322005107.GL9937@linaro.org>
2019-03-22 6:02 ` Heinrich Schuchardt [this message]
2019-03-22 7:12 ` [BUG] Cloning with git HEAD fails for some repositories Jeff King
2019-03-22 8:21 ` Wolfgang Denk
2019-03-22 9:31 ` Jeff King
2019-03-22 16:50 ` Eric Wong
2019-03-22 17:42 ` Heinrich Schuchardt
2019-03-22 18:09 ` Eric Wong
2019-03-22 18:41 ` Heinrich Schuchardt
2019-03-22 20:35 ` Eric Wong
2019-03-23 8:53 ` Jeff King
2019-03-24 12:07 ` [PATCH 0/3] fix dumb-http fetch with alternates Jeff King
2019-03-24 12:08 ` [PATCH 1/3] http: factor out curl result code normalization Jeff King
2019-03-24 12:09 ` [PATCH 2/3] http: normalize curl results for dumb loose and alternates fetches Jeff King
2019-03-24 12:13 ` [PATCH 3/3] http: use normalize_curl_result() instead of manual conversion 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=017964a9-bd75-5e36-0de7-57d4467d6a7e@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=takahiro.akashi@linaro.org \
--cc=wd@denx.de \
/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.
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 NNTP newsgroup(s).