Running "pkg upgrade" on FreeBSD results in:

Updating FreeBSD-ports repository catalogue...

sits there for ages

ran with -d:

DBG(1)[71664]> (fetch) libfetch> connecting
DBG(1)[71664]> (fetch) libfetch> fetching from: https://pkgmir.geo.freebsd.org/FreeBSD:15:amd64/latest/meta.conf with opts "i"

And it never downloads it.

Is libfetch badly broken?

pkg 2.7.4

(works fine in a browser)

#FreeBSD #pkg

@pertho Beware, browsers do funky stuff wrt name resolution. I'm not saying it is DNS, but...

@pertho I have had no problem with 2.7.4.

If a problem persists: more detail will help, however Mastodon is not suitable for this type of thing. I should recommend <https://billboard.bsd.cafe/category/6/freebsd> at BSD Cafe Billboard.

FreeBSD

The house blend. Discuss FreeBSD ports, jails, ZFS, and everything in between.

BSD Cafe Billboard

@grahamperrin It looks like a problem with the cluster:

https://github.com/freebsd/pkg/issues/2653

(reported by @vermaden )

Phew. I'm glad it's not just me.
Running pkg -f install pkg downgraded pkg from 2.7.4 to 2.6.2.

Weird.

#FreeBSD #pkg

pkg: truncated reply for signature_fingerprintsoutput, wanted 0 bytes · Issue #2653 · freebsd/pkg

On a fresh 15.0p5 system ... # pkg update -f Updating FreeBSD-ports repository catalogue... Fetching meta.conf: 100% 179 B 0.2 kB/s 00:01 Fetching data: 100% 11 MiB 1.9 MB/s 00:06 pkg: truncated re...

GitHub
@pertho @grahamperrin @vermaden oh lol that explains the issue I was seeing in some GitHub actions.