Re: Git core dump checking out main on armv7
- Reply: Mark Millard : "Re: Git core dump checking out main on armv7"
- In reply to: Mark Millard : "Re: Git core dump checking out main on armv7"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 19 Jun 2024 19:14:21 UTC
On Tue, Jun 18, 2024 at 10:22:25PM -0700, Mark Millard wrote: > > I'm going to quote kevens on discord from another git context: > > QUOTE > kevans: once you have git installed anongit via ssh is a lot more reliable, especially for the ports tree > END QUOTE > > (Watch out for my unusual directory naming on the left side of the lines:) > > If your context allows use of: ssh:// . . . > > # grep -rE "(^\[|url = )" /usr/*/.git/config > /usr/official-src/.git/config:[core] > /usr/official-src/.git/config:[remote "freebsd"] > /usr/official-src/.git/config: url = ssh://anongit@git.FreeBSD.org/src.git > /usr/official-src/.git/config:[branch "main"] > /usr/official-src/.git/config:[branch "stable/14"] > /usr/ports/.git/config:[core] > /usr/ports/.git/config:[remote "freebsd"] > /usr/ports/.git/config: url = ssh://anongit@git.FreeBSD.org/ports.git > /usr/ports/.git/config:[branch "main"] > > > I have historically found such more reliable than use of: https:// . . . > > ssh:// . . . can also be used on the command line. > > > If both ssh:// . . . and https:// . . . fail that likely has > implications different than if just one form does. Looks as if they both fail: # git clone --depth=1 -o freebsd ssh://anongit@git.FreeBSD.org/src.git /usr/src Cloning into '/usr/src'... remote: Enumerating objects: 104639, done. remote: Counting objects: 100% (104639/104639), done. remote: Compressing objects: 100% (88894/88894), done. remote: Total 104639 (delta 22165), reused 43690 (delta 11830), pack-reused 0 Receiving objects: 100% (104639/104639), 345.56 MiB | 1.34 MiB/s, done. Resolving deltas: 100% (22165/22165), done. fatal: missing blob object '619155cafe9277d1b3fc1bfd02fe76e27042a115' fatal: remote did not send all necessary objects # Both the "missing blob.." and "pack is corrupt..." messages have been seen regularly before. The system is running from microSD, but that didn't prevent cloning, checking out and building the existing system installation. Is there some way to check if the blob object named is actually present on the server? If not, that would be a clue. Thanks for writing! bob prohaska > > > === > Mark Millard > marklmi at yahoo.com > >