Re: git clone issues on 15.1-RELEASE on arm64
Mark Millard <[email protected]> Sat, 1 Aug 2026 13:05:37 -0700
| Newsgroups | gmane.os.freebsd.stable |
|---|---|
| Message-ID | <[email protected]> |
On 8/1/26 12:44, Nenhum_de_Nos wrote: > > > August 1, 2026 at 2:25 PM, "Mark Millard" <[email protected] > <mailto:[email protected]? > to=%22Mark%20Millard%22%20%3Cmarklmi%40yahoo.com%3E>> wrote: > > On 8/1/26 08:46, Nenhum_de_Nos wrote: > > August 1, 2026 at 10:47 AM, "Karl Denninger" <[email protected] > <mailto:[email protected]? > to=%22Karl%20Denninger%22%20%3Ckarl%40denninger.net%3E>> wrote: > > The problem appears to be at this point: > > Cloning into '/usr/src'... > fatal: unable to access 'https://git.freebsd.org/src.git/ > <https://git.freebsd.org/src.git/> <https://git.freebsd.org/ > src.git/>': <https://git.freebsd.org/src.git/%3E':> Resolving > timed out after 300226 milliseconds > > I do not know why, however, because my "base" source git clone has > in its config the following: > > [remote "freebsd"] > url = https://git.freebsd.org/src.git <https:// > git.freebsd.org/src.git> <https:// > git.freebsd.org/src.git> > fetch = +refs/heads/*:refs/remotes/freebsd/* > > And it works. > > I have several worktrees checked out against that since I build for > 14-STABLE and 15-STABLE at this point for distribution to machines > running ARM64 and AMD64. > > My latest "git pull --ff-only" to so-update was this morning. > > On 8/1/2026 09:36, Nenhum_de_Nos wrote: > > Hi, > > I have been fighting this issue for 2 weeks now, I guess its > time to ask here. The problem: > > root@arm_build_hd:/usr # rm -rf src/ > root@arm_build_hd:/usr # /root/git/freebsd_config/freebsd_git/ > src_git_checkout_15.1R.sh > Cloning into '/usr/src'... > fatal: unable to access 'https://git.freebsd.org/src.git/ > <https://git.freebsd.org/src.git/> <https://git.freebsd.org/ > src.git/>': <https://git.freebsd.org/src.git/%3E':> Resolving > timed out after 300226 milliseconds > root@arm_build_hd:/usr # /root/git/freebsd_config/freebsd_git/ > src_git_checkout_15.1R.sh > Cloning into '/usr/src'... > remote: Enumerating objects: 4850942, done. > remote: Counting objects: 100% (384686/384686), done. > remote: Compressing objects: 100% (29598/29598), done. > error: RPC failed; curl 56 OpenSSL SSL_read: OpenSSL/3.5.6: > error:0A000126:SSL routines::unexpected eof while reading, errno 0 > error: 73 bytes of body are still expected > fetch-pack: unexpected disconnect while reading sideband packet > fatal: early EOF > fatal: fetch-pack: invalid index-pack output > root@arm_build_hd:/usr # /root/git/freebsd_config/freebsd_git/ > src_git_checkout_15.1R.sh > you have mail > Cloning into '/usr/src'... > fatal: unable to access 'https://git.freebsd.org/src.git/ > <https://git.freebsd.org/src.git/> <https://git.freebsd.org/ > src.git/>': <https://git.freebsd.org/src.git/%3E':> Resolving > timed out after 300040 milliseconds > root@arm_build_hd:/usr # cat /root/git/freebsd_config/ > freebsd_git/src_git_checkout_15.1R.sh > git clone --branch releng/15.1 https://git.freebsd.org/src.git > <https://git.freebsd.org/src.git> <https://git.freebsd.org/ > src.git> <https://git.freebsd.org/src.git%3E> /usr/src > root@arm_build_hd:/usr # > > On two Orange Pi 5 Plus 16GB I have FreeBSD 15.1-R installed so > I can build opnsense for arm64 (this is not relevant for the > problem, except for one detail I will tell later). This box > above had 14.3-R running fine, all build times were fine, git > worked perfectly. Since I needed to upgrade to 15.1-R, git > stopped working as it was expected (and presented above). > > I looked for DNS reasons, changed DNS server, local server, > remote server, kept ping github.com while cloning, no good. I > started using the upgraded box, then I got another similar arm64 > box and installed fresh 15.1-R, everytime the same issue. The > one detail I told about opnsense building is that I use pkg > 2.3.1_1, as is the version that ships on the images and the port > is on opnsense ports github repo. Other than that, regular > FreeBSD 15.1-R. I download the github zip file for ports, run > make install on the pkg port and lock the package after. Used to > work fine, can this be the culprit? I got some messages after > upgrade about libpkg not the same version or database version. > But I then installed it all over and no more of that. > > So I tried to clone the repo today on a Linux Desktop here > (Linux Mint), all fine. Same network, same servers, same ISP. I > then tried on an old amd64 box running FreeBSD 15.1-R. Again, > fine. Both my arm64 failed, even after fresh install. Can the > pkg port be the one? Before I forget, both the arm64 run on > magnetic HDDs over USB adapter and all other run on SSDs over > SATA. Would this make this all happen? > > After several tries (3 days) I got to clone the repo and got to > start building. Ports used to take 24h and now runs for 5 days. > So I got info about llvm changes and got the config to try to > solve this (/etc/src.conf), and my point is just that, I need to > build vanilla FreeBSD 15.1-R on arm64 (just using older pkg, I > can try to not change now if people think may help) so I can > have world and kernel using llvm options from 14.X > > > Start distinct subject from the main point of your post: > > Were you successful at significantly decreasing that "5 days" time > frame? If yes, you may want to be very explicit about what you changed > that made the difference. > > The official arm64 build server build times suggests that 14.4 now takes > longer than 14.3 did --and that 15.1 takes even longer, as I remember. > > ("Suggests" is tied to: none of the examples are re-runs of the exact > same ports tree content --or, mostly, the same package subset. Comparing > the fairly uncommon attempts to rebuild everything tend to be what I > look at for such comparison/contrast activities.) > > End distinct subject. > > > > Mark, > > Unfortunatelly not yet. I need to rebuild it all first. > > the lines are: > > WITH_MALLOC_PRODUCTION=yes > WITHOUT_LLVM_ASSERTIONS=yes > WITH_LLVM_LINK_STATIC_LIBRARIES=yes > WITHOUT_PTHREADS_ASSERTIONS=yes There is also: WITHOUT_ASSERT_DEBUG=yes But see: <https://lists.freebsd.org/archives/freebsd-stable/2025-September/003110.html> for why official release builds do not do that. Also, as I remember, the usage of all 5 of these ignore the text after the = , even if that text is the likes of: no > > > on /etc/src.conf. > > matheus > -- === Mark Millard marklmi at yahoo.com