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.
FPGA programming and DragonFly
Thanks to yrabbit, there’s a full FPGA toolchain possible on DragonFly. It’s preliminary, but it works.
New package build for 6.0
I’m actually some days late in reporting this, but there’s a new full build of packages for DragonFly 6.0; it’s following the quarterly release schedule for ports, so 2021Q2 is the base.
This goes with the recent merges from -current into 6.0. Now is a good time to update your system completely, if you have not already.
One more reminder about pkg
If you are upgrading an older 5.8.x system to DragonFly 6, and get a lua error when updating pkg: manually copy over a config file, and you’ll be set.
DragonFly 6.0 is out!
DragoFly 6.0 is tagged and ready for download. There’s ISO images and of course you can upgrade using the notes on the release page. One of the improvements in this release cycle is improved dsynth support, so of course there are many prebuilt packages available; don’t forget to update those too.
6.x packages posted
With good timing, 6.x packages are now available for those of you who need them.
New packages available
There’s a new build of binary packages available, for both 5.8 and DragonFly-current.
A reminder: updating pkg
I’ve mentioned it before but it came up again, so it’s worth repeating: your 5.8 install of DragonFly may need an update of the pkg tool.