schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
boostedWow. The updates to the #php packages in #pkgsrc were updated to 8.5.12, 8.4.27 and 8.3.36, respectively, by 1358Z. Building and in-place update went smoothly. My #nextcloud is patched and back in operation.
I'm impressed. Thank you!
#NetBSD #homeserver #selfhosting.
boostedReally pleased to have helped the test framework for compat_linux for #NetBSD land in #pkgsrc today:
https://pkgsrc.se/emulators/compat_linux_test_project
So get testing and fixing those low-hanging fruit!
It has a ring of Debian kFreeBSD to it.
But there's more to it than APK instead of #pkgsrc. It's based around @ska's #s6 and #execline and suchlike. Of course, those are also available on actual #NetBSD too.
I suspect that it's not aimed at people who want to switch operating systems as such, but at people who use #AlphineLinux but who do not want to have #Linux as part of that any more.
boostedJust uploaded the #ChiPass (the slopless fork of the KeePassXC package manager) and #Fooyin (a QT-based music player with an anti-LLM policy and a cool UI) to the wip repo of #PKGSRC, a tool used for building packages for many OSes and the native packaging system for #NetBSD. They're available as "wip/chipass" and "wip/fooyin" if you want to try them out. Let me know if you have any problems.
If you haven't set up wip already, you'll need to clone the repo for it inside of the main PKGSRC repo.
At the moment both have patches to fix pathing issues under NetBSD, I'll hopefully have time later today file some bugs later today to try to fix these upstream.
If you are using my macOS packages available from https://pkgsrc.smartos.org/install-on-macos/ then note that due to newer compiler and SDK requirements, the 14.5 package set will no longer be updated, and there is a newer 15.5 SDK target now available.
Upgrade instructions are available here: https://mail-index.netbsd.org/pkgsrc-users/2026/10/15/msg043607.html
@algernon FWIW I did exactly this for a while at https://pkgsrc.smartos.org/install-on-netbsd/ but it wasn't that popular so I stopped the updates and re-used the machine for normal pkgsrc testing and bob development. I do wonder with the recent interest whether it would be worth starting it up again though (and obviously upgrade to 11.0)
boosted#NetBSD newcomers will find this interesting #NASA @NASA uses #pkgsrc for NAS with their Linux system
https://www.nas.nasa.gov/hecc/support/kb/using-software-packages-in-pkgsrc_493.html
boostedAdvanced Programming in the #UNIX Environment
Week 5: make(1)
Let's take a look at how the make(1) utility can be used to help us selectively build our code project. You don't need much to get started -- built-in default suffix rules make this easy -- but with time you can build complex build frameworks (see, e.g., #NetBSD's #pkgsrc system). We'll leave the question whether or not make(1) is Turing-complete for another day...
I am updating #pkgsrc/lang/wasi-libc to fix build of pkgsrc/www/firefox-158 with LLVM 22.
pkgng was not a precise drop-in replacement for the old system, and there are these differences in command-line usage.
But I personally think that they pale in comparison to #Debian where one has to remember whether the command one wants is dpkg, one of the dpkg-* ones, apt, one of the apt-* ones, or perhaps aptitude.
And there are subtle differences between dist-upgrade, safe-upgrade, and full-upgrade.
That's before we even reach the wider world of pacman/rpm/dnf/emerge/zypper/apt-cyg/apt-get/yum.
Or tix, for that matter, which has no 'info' subcommand, according to its manual. (-:
https://pub.sortix.org/sortix/release/nightly/man/man8/tix.8.html
boostedUpdated binary packages on my T430 #NetBSD Laptop yesterday using #pkgsrc 2026Q3. All went great.
Note one minor thing, if you move to #emacs31 you may need to add this exact line to the very first line of ~/.emacs and any other personal .el files:
;; -*- lexical-binding: nil -*-
This will avoid an error prompt about lexical-binding on statrup.
I was already a little annoyed that Apple replaced rsync with openrsync, as it broke some of my own personal ways of working (e.g. listing remote directories), but now the version in macOS 27 is also breaking "bob publish" because it has an incompatible --delete-excluded implementation.
#pkgsrc to the rescue once again, but please stop breaking things.
@r1w1s1 @ParadeGrotesque I hope I'm not stepping on anyone's toes, and apologies for "short-circuiting" the eh Makefile, (which looks like it took a lot of time was spent on it), but I added eh version 1.9.0 to #pkgsrc as editors/eh https://mstdn.social/@pkgsrcchanges/117396740146577723
editors: Makefile
editors/eh: DESCR Makefile PLIST distinfoagc: Add and enable editors/eh, version 1.9.0, to the packages collection
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/editors/Makefile.diff?r1=1.270&r2=1.271
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/editors/eh/DESCR?rev=1.1
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/editors/eh/PLIST?rev=1.1
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/editors/eh/distinfo?rev=1.1
Bit disappointing.
Upgraded pkgsrc macOS build host from 14.x to 27.0.1, and MacFUSE to latest.
First run is showing consistently slower builds.
bindfs CPU usage seems higher, but I don't have accurate numbers on that. Also there is still the 2 minute delay to unmount /System.
Maybe next year?
The most likely causes were the calls to ctype functions in xft_word_wrap(), but those were changed to use unsigned char in 6.15. So if this really is 6.15 as claimed, the ctype negative character bug is no longer there to be hit, from a cursory inspection.
The sensible first step would be to get a core dump.
@mrgtwentythree @stefano@bsd.cafe @dch @stefano@rpi0w.stefanomarinelli.it Feeling rather guilty we didn't get it into #pkgsrc for 2026Q3 given it's been on #NetBSD throughout its development especially as #FreeBSD had a Day 1 release
@gourd #pkgsrc knows all about this, so you could knock up your own local package and take advantage of that infrastructure. Take a look at gam; the penultimate two lines do the magic:
https://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/gam/Makefile?rev=1.28;content-type=text%2Fplain
Hey folks!
I have written some travel notes from EuroBSDCon 2026, Brussels, Belgium:
https://blog.NetBSD.org/tnf/entry/eurobsdcon_2026_in_brussels_belgium
The conference was amazing and I had a lot of fun and learned a bunch!
Thanks to everyone who made it possible!
#EuroBSDCon2026 #EuroBSDCon #NetBSD #pkgsrc #FreeBSD #OpenBSD
For those of you who follow this thing, I just realized I missed the announcement that pkgsrc 2026Q3 was released on 26th September, 2 days ago!
Thanks to @bentsukun and all the wonderful people behind #pkgsrc ...
(it will never be not funny that the announcement on their web page always lags behind the official release message) 😄
boosted@Unsightly3055 We don't decide on which software to port to pkgsrc or not, it's just around 100 of us, plus contributors, who spend time creating and updating packages for things that we use.
We love it when people get involved and help out packaging up the software that they like and need, and we're looking forward to welcoming new contributors as they migrate from Linux.
Until then, yeh you can usually run Linux binaries using the emulation, or even still run VMs for a bit.
I have just ported Presto server to NetBSD. It is trivial however running without launcher.py was difficult. I will add it to #pkgsrc later.
I have confirmed that #pkgsrc/www/firefox-156 is ready to commit to pkgsrc tree. However I found 156.0.1. I will commit my update tomorrow.
📦 pkgsrc Is Cool // Wisellama
「 Pkgsrc is NetBSD’s package manager, but thanks to NetBSD’s portability philosophy, pkgsrc is fully supported as a package manager on other Unix-like operating systems like Linux, Mac, and Solaris. It supports installing binary packages, but the reason I was interested in it is that pkgsrc supports building packages from source as well 」
https://www.wisellama.rocks/posts/2021-12-23-pkgsrc-is-cool/
Both nettle and and mbedtls3 are packaged in #pkgsrc. So it looks like the only things missing are pihole-FTL, which is probably fairly straightforward to package, and a version of that vast install shell script that doesn't have all of the wacky creating secret packages nonsense in it and just does the configuration parts. (pkgsrc itself can handle creating and depending from a pihole-meta package.)
Today's rabbit hole:
* gitea broken due to sqlite.go update
* sqlite.go blocked by libsqlite3.go
* libsqlite3.go blocked by libc.go
* fix libc.go
* libsqlite3.go now blocked by upstream sqlite bug
* caused by "-Wl,-R" in shell scripts getting brace expanded when converted to tcl array
Turtles.
Hmm... #pkgsrc/audio/pavucontrol does not drawn properly by pkgsrc/wip/mesa-26. It emits DRI3 error storm.
The Xu #Debian #AlmquistShell now has a patch for ;& in case statements.
This is against the latest Xu version, so should be a fairly simple drop-in for everyone who builds from that, including #FreeBSD ports, #pkgsrc, and so forth.
I'm not entirely happy about the EV_EXIT flag interaction, and how -e is supposed to affect case fallthrough.
#pkgsrc/wip/mesa-26 works fine for me. pkgsrc/www/firefox-155.0.1 does not crash anymore when F11 key is pressed.
While I am a firm believer in using all available tools to improve the software I work on, I do really like that NetBSD's firm and unequivocal anti-LLM stance is proving popular, and helping it to gain traction.
To all the new users I'm seeing over the past few weeks, welcome! Hope we can help you get up and running.