On Mon, May 11, 2026 at 03:25:04PM +0000, Shawn Webb wrote: > Hey all, > > It appears something's amiss in the FreeBSD ports repo: > > ==== BEGIN LOG ==== > $ git fetch upstream > remote: Enumerating objects: 782, done. > remote: Counting objects: 100% (530/530), done. > remote: Compressing objects: 100% (10/10), done. > remote: Total 782 (delta 524), reused 520 (delta 520), pack-reused 252 (from > 1) > Receiving objects: 100% (782/782), 872.09 KiB | 173.00 KiB/s, done. > Resolving deltas: 100% (578/578), completed with 497 local objects. > From ssh://git.FreeBSD.org/ports > bd02c95174ef..8bdb30c6d549 2026Q2 -> upstream/2026Q2 > 39fabf7c0bc8..b7d1ffb8f542 main -> upstream/main
As of this writing, b7d1ffb8f542 is the most recent commit shown in the archives of dev-commits-ports (at https://lists.freebsd.org/archives/dev-commits-ports-main/2026-May/date.html). > shawn-framework-01[shawn]:/usr/ports $ git merge upstream/main > fatal: unable to read blob object e5a98d716225916ee8024ebf9d1ad2b6e8c58ced There is no entry in the above-cited archives for a commit that would match that hash. > $ git remote -v > github [email protected]:HardenedBSD/ports.git (fetch) > github [email protected]:HardenedBSD/ports.git (push) > origin [email protected]:HardenedBSD/ports.git (fetch) > origin [email protected]:HardenedBSD/ports.git (push) > rad rad://z2XrdvALg77ycnuZRXgScb27yb3wM (fetch) > rad > rad://z2XrdvALg77ycnuZRXgScb27yb3wM/z6Mkp9s3W8zN2qigmUirtvJ8NesXXZkYsYC6XEjdGcSXFeeR > (push) > tor [email protected]:HardenedBSD/ports.git (fetch) > tor [email protected]:HardenedBSD/ports.git (push) > upstream ssh://[email protected]/ports.git (fetch) > upstream ssh://[email protected]/ports.git (push) > ==== END LOG ==== > > `git show e5a98d716225916ee8024ebf9d1ad2b6e8c58ced` shows the commit, > but only the payload, not the commit message. > .... My last local update for ports was at main-n746034-8c7b79314654 ("archivers/p5-Archive-Tar: update to 3.06"); my local private mirror, when asked about e5a98d716225916ee8024ebf9d1ad2b6e8c58ced, does not whine ("fatal: bad object ..."), as it does for a hash that does not correspond to a commit... but it also declines to say anything at all about it (using "git log" or "git show"): g1-120(15.1-S)[12] dirs /usr/ports g1-120(15.1-S)[13] git show -n 1 e5a98d716225916ee8024ebf9d1ad2b6e8c58ced | hd g1-120(15.1-S)[14] git log -n 1 e5a98d716225916ee8024ebf9d1ad2b6e8c58ced | hd g1-120(15.1-S)[15] echo $? 0 Peace, david -- David H. Wolfskill [email protected] See https://www.catwhisker.org/~david/publickey.gpg for my public key.
signature.asc
Description: PGP signature
