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.
Hmm... I am busy recently. Firefox 153 is coming. A test for my patch to fix build failure of #pkgsrc/www/firefox-152 under NetBSD/i386 will be in final stage.
Building pkgsrc with bob on NetBSD: if you get an error about X11R7, this is normal if you have a headless server without Xorg/X11.
Comment out the following line in your configuration file: { action = "mount", fs = "null", dir = "/usr/X11R7", opts = "-o ro" },
See https://github.com/jperkin/bob/blob/main/config/netbsd.lua#L152
Of course if you need to build X11 apps, install X11 on your host and keep the line.
Now that I want to keep gotosocial and readeack pkgsrc packages up to date automatically, I find myself trying bob.
Not bob the playschool user interface from Microsoft.
Bob from @jperkin the pkgsrc building sandboxed factory written in rust.
Will see how it goes...
@readeck Hello there, I did some work to build Readeck on NetBSD:
For testing, and standalone installations: platform specific Makefile, diff patch and README files, will submit a PR on Codeberg 🙂
For production : a package for the pksrc repository (WIP), NetBSD 10.1 amd64 build available here https://pepperm.int.eu.org/pkgsrc/packages/All/readeck-0.22.3.tgz (will be submitted to pkgsrc)
Happy notes on Readeck 🙂
boosted✅ Successful gotosocial-0.22.0 (new stable major release) build and package available here https://pepperm.int.eu.org/pkgsrc/packages/All
From now on, this GTS version is stable: further upgrades will only be available from pkgsrc repository and GTS Codeberg repository (no need for me building -rc packages anymore, that's a good thing).
✅ Submitted a package update to pkgsrc-WIP for v0.22.0, with help of wiz it should be good.
One may use pkgin or NetBSD pkg_add tools to upgrade GoToSocial from now on.
Careful about releases notes and configuration or database breaking changes.
Build platform: NetBSD 10.1 amd64 / pkgsrc trunk
Compilation and linker flags aligned with GTS binary release on Codeberg
✅ Successful gotosocial-0.21.3 (current stable) build and package available here http://pepperm.int.eu.org/pkgsrc/packages/All/
✅ Submitted a package update to pkgsrc-WIP for v0.21.3, with help of wiz it should be good
Build platform: NetBSD 10.1 amd64 / pkgsrc trunk
Compilation and linker flags aligned with GTS binary release on Codeberg
boosted#NetBSD #pkgsrc 2026Q2 is now fully underway.
There’s no easy way to move a kernel from NetBSD to an AmigaOS partition, so I had to xz it, split it, copy it over using MS-DOS disk images using a Gotek with FlashFloppy, then join and xz -d on the Amiga side.
#m68k is really taking off! The virt68k port that @thorpej has made is nothing short of amazing. It can now compile practically anything in a VM with 3 gigs of memory and 4 gigs of swap, faster than a real m68060.
This lets us compile large packages that weren’t previously possible or that required a lot of manual tweaking, like llvm-21.1.8, clang-21.1.8, webkit-gtk-2.36.8nb29.
More to come!
boosted
boosted@gotosocial @netbsd ✅ Successful gotosocial-0.22.0-rc3 build and package available here https://pepperm.int.eu.org/pkgsrc/packages/All/
Build platform: NetBSD 10.1 amd64 / pkgsrc trunk
Compilation and linker flags aligned with GTS binary release on Codeberg
Will submit a package update to pkgsrc-WIP when GTS reaches 0.22.0-GA 😊
Ah, #pkgsrc 2026Q2 shipped early, yay.
https://mail-index.netbsd.org/pkgsrc-users/2026/06/23/msg043060.html
boostedSlowly working on updating @gotosocial package in @netbsd’s pkgsrc tree…
Target : be ready with a working package for GTS 0.22 GA release 🤞
@agc Digging deeper, I found where #PostgreSQL versions are configured for #pkgsrc builds:
../../mk/pgsql.buildlink3.mk
PGSQL_VERSION_DEFAULT?= 16
PGSQL_VERSIONS_ACCEPTED?= 18 17 16 15 14 13
That clears up the "Use the 16, Luke" mystery. I'll report that 13 is off the table as there is no client.
$ pkgin se "postgresql1[3-9]-client"
postgresql14-client-14.23 = PostgreSQL database client programs
... 15 16 17 ...
postgresql18-client-18.4 PostgreSQL database client programs
boostedportability(TM) #netbsd #pkgsrc #tigersrc
* alix3d3 (i586) - it finds out what uses SSE2 when it shouldn't
* er4 (evbmips64n64eb) - it finds out when things hardcode a list of supported archs
* mac mini (powerpc; usually runs darwin) - it finds out when things don't specify a c/c++ lang std
* olimex a64 (aarch64) - it finds out when the arm drivers get too piney.
* banana pi (earmv7hfeb) - ugh.
* blade 150 (sparc64, bottom) - it finds out EVERYTHING.
100% not running 24/7.
"
pkg_add: Installed package `postgresql14-client-14.23' conflicts with `postgresql1[0-35-9]-client-[0-9]*' when trying to install `postgresql16-client-16.14'.
"
Wait. What?
is there someone on here who uses #pkgsrc with #macos ?
i can download #alacritty with pkgsrc now, but the version it installs for macos doesn't seem to be the version i can download from github -- it isn't installed to /Applications and has to be bootstrapped via Terminal.app to run.
are there any clever/simple ways to rig this up? am i missing something obvious?
boostedDelighted to announce the first 1.0.0 release of bob, and import it into pkgsrc for general use in time for pkgsrc-2026Q2.
https://mail-index.netbsd.org/pkgsrc-changes/2026/06/12/msg348092.html
One of the reasons for the name is in honour of my dad, who has later stage dementia.
I've poured a lot of effort into making this program be the best it can be, so that it is befitting of its name.
It's something I've wanted for many years, and I'm thrilled that it's now available. I think it's pretty great, and I hope you do too.
Released bob v0.99.7, available via 'cargo install bob' or pkgsrc-wip/bob.
Includes a whole host of performance wins, memory use reductions, new commands, ergonomic improvements, reliability fixes, and general code cleanups.
Aiming to release this as v1.0 ready to import into pkgsrc for the next branch, so if you have any issues with it please let me know as soon as possible!
https://github.com/jperkin/bob/blob/main/CHANGES.md
Happy building.
@michael_croes Dans #pkgsrc, tu trouveras également sysupgrade, ce qui est bien plus facile. Un simple « sysupgrade auto » suivi d’un redémarrage suffit.
EuroBSDCon 2025 in Zagreb, Croatia was great!
At NetBSD devsummit I have presented «Running Docker (and more) in NetBSD via Lima». Lima (<https://lima-vm.io/>) permits to run Linux virtual machines (as guests) - with port forwarding and volumes sharing - and I have showed how NetBSD is supported and works as host!
Slides available at <https://www.NetBSD.org/gallery/presentations/leot/eurobsdcon2025-devsummit-lima/lima.pdf>.
I have now also imported Lima in pkgsrc as sysutils/lima.
boostedI just updated my #pkgsrc wip packaging for the #VimClassic 8.3.0 release. It's working just fine on my #NetBSD 11 dev host.
If you want to test it, see the https://pkgsrc.org/wip/ docs here. I'm going to live with for a couple days and see about getting it pulled into main.
はてなブログに投稿しました
NetBSD/amd64,i386 11.0_RC4 ておくれLive Image 20260601版 - tsutsuiの作業記録置き場
https://tsutsui.hatenablog.com/entry/teokure20260601
#はてなブログ #NetBSD #pkgsrc #mikutter
boostedhey #netbsd people! On 11.0_RC4 I have an issue with haproxy 3.3.5 from #pkgsrc 2025Q1. It randomly fails with:
/usr/src/crypto/external/apache2/openssl/dist/ssl/record/methods/tls_common.c:1902: OpenSSL internal error: Assertion failed: rl->nextwbuf >= rl->numwpipes || TLS_BUFFER_get_left(&rl->wbuf[rl->nextwbuf]) == 0
It had been working fine for months before I upgraded to 11.0_RC4. Any ideas how to tshoot it further?
bug report: https://gnats.netbsd.org/60292
The #pkgsrc version of rsync says 3.4.3 but the builds say 3.4.1 or earlier.
https://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/net/rsync/index.html
boostedFirst SmartOS pkgsrc build using GCC 15.2.0. As expected, plenty of fallout due to the ongoing strictness changes in upstream GCC.
https://reports.pkgci.org/SmartOS/upstream/trunk/20260518T093149Z/report.html
Hopeful that there are only a few high-profile blockers, and that the gmake failure is not more systemic gnulib-type issues where all individual releases bundle their own broken copies.
@veer66 Why not create your own pkgsrc entry (ie directory, Makefile, distinfo, DESCR, PLIST and any patches) for your own software? Maybe add it to #pkgsrc-wip so everyone can use it?Then you won't be breaking abstractions, and you and others can use it on other autotools-supported platforms you may not have access to (pkgsrc makes sure config.sub and config.guess are consistent everywhere)