pin Don't know anything about FreeBSD but, could this be a mirror problem
it's a known problem on FreeBSD since, well, ever 😆
20-100 They find it natural that everybody installs her own Poudriere server to build from source
So true. No harm meant, poudriere is an utterly amazing tool, but it may not fit the use case of the casual workstation user. By the way, for desktop use, I definitely prefer synth, as it tends to automatize stuff and has sane defaults. FreeBSD always felt like the Gentoo of BSDs (and it's not a secret the latter was inspired by the former): very powerful, high performance, great abstraction and flexibility, unparalleled potential for customization and use-specific configurations; but it may fall short in the long period (speaks the one who uses pkg_comp on NetBSD), unless you stick with pre-compiled packages and their defaults (which tbh are not that great, and often server-oriented).
20-100 And finally, when a package fails to build on FreeBSD's Poudriere servers, it disappears from the repository (instead of keeping the previous version) and if you update your machine, the working version gets removed.
I can relate
bsduck You can also lock the affected package (# pkg lock yourpackage).
This, pkg lock is a life saver
bsduck encountered much more missing packages (and for a longer time) when experimenting with NetBSD
You're right, though it often comes down to opting for the ''right" (most convenient, be it even compiled for a minor release behind) repo, and fortunately there's many unofficial ones available out there.
bsduck OpenBSD is definitely the most reliable here, which is not a surprise since they mostly use packages only and using ports is officially discouraged