New ๐๐ฟ๐ฒ๐ฒ๐๐ฆ๐ ๐ฃ๐๐๐๐๐ฆ๐ ๐ ๐ถ๐ป๐ผ๐ฟ ๐จ๐ฝ๐ด๐ฟ๐ฎ๐ฑ๐ฒ๐ [FreeBSD PKGBASE Minor Upgrades] article on vermaden.wordpress.com blog.
https://vermaden.wordpress.com/2026/05/10/freebsd-pkgbase-minor-upgrades/
#verblog #beadm #bectl #server #desktop #freebsd #laptop #pkg #pkgbase #zfs
New ๐๐ฟ๐ฒ๐ฒ๐๐ฆ๐ ๐ฃ๐๐๐๐๐ฆ๐ ๐ ๐ถ๐ป๐ผ๐ฟ ๐จ๐ฝ๐ด๐ฟ๐ฎ๐ฑ๐ฒ๐ [FreeBSD PKGBASE Minor Upgrades] article on vermaden.wordpress.com blog.
https://vermaden.wordpress.com/2026/05/10/freebsd-pkgbase-minor-upgrades/
#verblog #beadm #bectl #server #desktop #freebsd #laptop #pkg #pkgbase #zfs
RE: https://mastodon.bsd.cafe/@grahamperrin/116525622004630724
pkgbase in the FreeBSD Handbook
<https://reviews.freebsd.org/D56632> for <https://docs.freebsd.org/en/books/handbook/cutting-edge/#pkgbase> seems to be an outcome from the Foundation-supported hackathon.
I provided minor corrections, but abstained from using Phabricator to provide them.
@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.
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...
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)
@justine
Looks quite simple port without patch.
But reading the description, it seems to be a wrapper for specific syscall with the same name as the port.
So it would depend if the syscall exists on #OpenBSD and compatible with the one on #FreeBSD.
If #OpenBSD matched above prerequisite, and #OpenBSD ports infrastructure is enough alike with #FreeBSD #ports (IIRC, #NetBSD, the direct origin of #OpenBSD, once introduced #FreeBSD #ports framework far before when it was still quite simple and switched to their own #pkgsrc later), the conversion would be trivial.
On #FreeBSD, porters (including myself) first create a port under specific category directory such as graphics, test, hook on category Makefile, generate diff and file a PR on Bugzilla and/or open review on Phabricator.
For any #ports that are not intended to be included in official #ports, no need to hook to category Makefile and no need to file PRs / opening reviews. Ports framework allows it. Hooking on category Makefile is needed to be picked for official #pkg building. Maybe #OpenBSD #ports, too, as without the allowance, how porters attempt to make new ports?
By searching Internet, found this.
https://www.openbsd.org/faq/ports/guide.html
And FreeBSD has a (large) document "Porter's Handbook".
https://docs.freebsd.org/en/books/porters-handbook/
An example how I've added new FreeBSD port.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293719
https://reviews.freebsd.org/D55798
And its relevant commit.
https://cgit.freebsd.org/ports/commit/?id=b23b14c3bfc0d930f7757226b06a88008e95909c
Maybe #OpenBSD would have its own workflow, though.
#FreeBSD 's #pkg 2.7.0 is out!
Highlights:
- Per-package triggers (with pkg_upgrade variable)
- Install directly from http://, https:// or file:// URLs
- Switched back to libfetch
- Solver fixes for multi-repo setups, fewer spurious reinstalls
- autoremove now aware of install/delete/upgrade
- search -S comment-description, query %y/%Y for provides/requires
- Tons of crash, memory leak and portability fixes
#FreeBSD "#pkg-update(8)" is having issue right now ...
Updating FreeBSD repository catalogue...
pkg: Failed to fetch https://pkg.FreeBSD.org/FreeBSD:14:amd64/latest/meta.conf: SSL peer certificate or SSH remote key was not OK
...
Nevermind: Looks like severe time difference between its #clock & of the host of its virtual machine. Restart fixed it.
RE: https://mastodon.bsd.cafe/@grahamperrin/116281872164093377
@_bapt_ @emaste maybe the pkg-unregister(8) manual page can gain an example:
pkg unregister -f FreeBSD-\*
The example was given by Emmanuel Vadot in December 2025 at the foot of <https://mail-archive.freebsd.org/cgi/mid.cgi?20251202162711.16aec122152219f614c30beb>.
<https://man.freebsd.org/cgi/man.cgi?query=pkg-unregister&sektion=8&manpath=freebsd-ports#EXAMPLES> (the EXAMPLES page anchor does not yet exist).
<https://github.com/freebsd/pkg/blob/e88f7ab64889548e841ccd0bb2972ea6efec1152/docs/pkg-unregister.8#L139-L142> between the FILES and SEE ALSO sections of the page.
Thanks
vermaden
vermaden
Graham Perrin
Tom
TomAoki
bapt
ax6761