Re: Weird git issue this morning

Shawn Webb <[email protected]> Mon, 11 May 2026 16:01:47 +0000
Newsgroups	gmane.os.freebsd.devel.ports
Message-ID	<r6qli5s26bweu54yoohgczlghzrfu2myo6vtd43dixazycjcau@wxwpbf5owlad>
On Mon, May 11, 2026 at 08:42:54AM -0700, David Wolfskill wrote:
> 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

The commit can be found here, too:
https://cgit.freebsd.org/ports/commit/e5a98d716225916ee8024ebf9d1ad2b6e8c58ced

It's currently the HEAD of the FreeBSD ports tree.

Thanks,

-- 
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

Signal Username:  shawn_webb.74
Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50
https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc
signature.asc (application/pgp-signature, 833 B)