If you have a bulk build of packages happening with dsynth(1), you can now add – literally, that’s the command – to the package list without interrupting the build.
Moving dsynth
If you’re moving your dsynth build to a different machine, there’s now a ‘list-system’ directive that lets you recreate the same setup in a new place.
Where the (dports) action is
I mentioned a new committer for DragonFly, Sergey Zigachev, recently. He hasn’t shown in the commit logs for DragonFly directly – cause he’s fixing up dports. I’m mentioning that because the amount of work that goes into dports to keep all those ports working on DragonFly is separate and unseen – but necessary.
New dports, new point release
There’s a new dports build, and there’s been some updates so a new point release to 6.2.2 for DragonFly is a good idea. The new binary packages are available now with ‘pkg upgrade’, and I’ll work on 6.2.2 over the next few days.
New US mirror for DragonFly
Sandy River is the newest DragonFly mirror, with ISOs and dports packages.
New binary packages for DragonFly
It’s based off 2022Q1 from FreeBSD Ports, and it’s available now through pkg.
pkg and Meta v1 support
If you run pkg on DragonFly and get a warning about “Meta v1 support ending”, it’s only a warning. It will go away on its own.
Rebuilding samba
If you are running bleeding-edge DragonFly _and_ installed the newest dports binary package build _and_ you are using Samba, you may need to update and rebuild.
New 2021Q4 binary packages
There’s a new build of binary packages for DragonFly, based off the 2021Q4 quarterly ports release. This will require an upgrade of most if not all packages cause of a switch from LibreSSL to OpenSSL as the default SSL library.
dsynth updates
DragonFly 6.0.1 released!
6.0.1 is tagged and available. The major reason for this update is an expired Let’s Encrypt certificate that would cause problems when downloading dpkg binaries. A list of 6.0.1 commits is available.
I recommend the usual rebuild process mentioned on the 6.0 release notes:
make buildworld
make buildkernel
make installkernel
make installworld
make upgradeDon’t forget to update your packages with ‘pkg upgrade’.
Let’s Encrypt cert problem fixed
If you have encountered that problem with Let’s Encrypt and dports, the fix is committed and a make world is needed.
Let’s Encrypt certs and pkg
You may get some errors because of an expiring base Let’s Encrypt certificate when using pkg. It’s being worked on.
Keeping a package unchanged
The recent tmux package update reminds me to mention ‘pkg lock’. When you update packages, pkg will update everything. If there’s a package you don’t want changed, the pkg lock(8) command will keep it at the current version. There can be some other packages held back because of dependencies, but that’s OK. Don’t forget to pkg unlock when no longer needed…
tmux post fixed
If you want to update to the now fixed tmux port, you’ll want to add a -f to the pkg command to force it; the version number hasn’t changed.
tmux port redo
If you’re upgrading to the latest dports, and you use tmux – don’t update that particular port yet.
New quarterly packages available
tuxillo has built a new set of packages for dports; upgrade using the instructions in his post. (Though ‘pkg upgrade’ has generally worked for me as the quickest solution.)
NVMM, qemu, and dports
I think from this commit that qemu in dports is able to build NVMM-compatible. It won’t be in the current binaries for download because those are built from quarterlies, but work from source.
I am not sure those sentences I just typed would be comprehensible to a non-BSD user.
How big is chromium?
Here’s a link to a commit for dsynth that gives an idea of how huge a debug build of chromium can be.
Working Wireguard on DragonFly
This note from James Cook describes how to get Wireguard functioning on DragonFly; his linked patch is not necessary at this point since it’s been committed to dports – though not in the latest binaries.