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.
boosted@bpl a better tip is to just install pkg_alternatives and then the wrappers are automatically created and updated regardless of which version of ffmpeg you choose to have installed.
I'll concede that the user interface for pkg_alternatives is .. sub-optimal, but once installed it's mostly fire and forget
@brubarwal @ParadeGrotesque Yeh it's a common issue, especially when you add CDNs into the mix. The only way for pkgin to work reliably is if entire package directories are only ever updated atomically. I do this for https://pkgsrc.smartos.org/ so you'll never see similar errors there, but I don't know that everyone else is so careful. If you just run naive rsync then files and pkg_summary will be out of sync until the entire directory has finished uploading. #netbsd #pkgsrc
Decided to dig into what I initially suspected was hardware issues on a host performing "pkgin upgrade" very slowly.
No, turns out it's legitimate requests hammering the disks, with pkg_delete performing an MD5 check on every file it is about to forcibly remove anyway.
Eventually it'd be nice to add a flag for this, but for now I've removed it for my builds:
https://github.com/TritonDataCenter/pkgsrc/commit/87055e3a0c53f409a0cf1efa887a3cb96afe0757
This will be in macOS and SmartOS builds soon, and will significantly improve upgrade performance.
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.
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!
boostedAh, #pkgsrc 2026Q2 shipped early, yay.
https://mail-index.netbsd.org/pkgsrc-users/2026/06/23/msg043060.html
@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.
はてなブログに投稿しました
NetBSD/amd64,i386 11.0_RC4 ておくれLive Image 20260601版 - tsutsuiの作業記録置き場
https://tsutsui.hatenablog.com/entry/teokure20260601
#はてなブログ #NetBSD #pkgsrc #mikutter
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.