#pkgsrc — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #pkgsrc, aggregated by home.social.
-
Excited to try this, have wanted a Rust alternative to ShellCheck for a long time now.
https://github.com/ewhauser/shuck
The main issue with ShellCheck is that the Haskell infrastructure in pkgsrc is sub-optimal, and it currently pulls in the full ghc as well as lots of hs-* dependencies.
This brings the total disk size required for a simple tool to 2.5GB(!), and a lot of additional downloads for every update.
~/.cargo/bin/shuck on the other hand is a much more reasonable 22MB.
-
Excited to try this, have wanted a Rust alternative to ShellCheck for a long time now.
https://github.com/ewhauser/shuck
The main issue with ShellCheck is that the Haskell infrastructure in pkgsrc is sub-optimal, and it currently pulls in the full ghc as well as lots of hs-* dependencies.
This brings the total disk size required for a simple tool to 2.5GB(!), and a lot of additional downloads for every update.
~/.cargo/bin/shuck on the other hand is a much more reasonable 22MB.
-
@wideshut Yep, I've been using #pkgsrc on macOS for about 20 years. @jperkin even provides binary packages these days - https://pkgsrc.smartos.org/install-on-macos/
-
はてなブログに投稿しました
NetBSD/amd64,i386 11.0 ておくれLive Image 20260809版 - tsutsuiの作業記録置き場
https://tsutsui.hatenablog.com/entry/teokure20260809 -
はてなブログに投稿しました
NetBSD/amd64,i386 11.0 ておくれLive Image 20260809版 - tsutsuiの作業記録置き場
https://tsutsui.hatenablog.com/entry/teokure20260809 -
I've been working on some optimisations to bob's dynamic scheduler, which has resulted in a huge new personal best for a from-scratch pkgsrc bulk build:
Built 26943 in 17h 40m 23s (22688 succeeded, 0 cached, 2577 failed, 1678 skipped)
Not quite an apples-to-apples comparison as I've been using a slower host but with more cores, but previously this was taking just under 24 hours.
-
I've been working on some optimisations to bob's dynamic scheduler, which has resulted in a huge new personal best for a from-scratch pkgsrc bulk build:
Built 26943 in 17h 40m 23s (22688 succeeded, 0 cached, 2577 failed, 1678 skipped)
Not quite an apples-to-apples comparison as I've been using a slower host but with more cores, but previously this was taking just under 24 hours.
-
If you're running the SmartOS trunk package set, then ensure you have the latest pkg tools installed:
$ pkg_add -U pkg_install pkgin
This will help avoid a potential issue I discovered when upgrading a host that hadn't been updated for a long time:
For now I've only published the "tools" set, I'll hold off a bit before publishing the main x86_64 set to ensure everyone is ready.
Apologies if you hit this. The modern versions are a lot more robust.
-
If you're running the SmartOS trunk package set, then ensure you have the latest pkg tools installed:
$ pkg_add -U pkg_install pkgin
This will help avoid a potential issue I discovered when upgrading a host that hadn't been updated for a long time:
For now I've only published the "tools" set, I'll hold off a bit before publishing the main x86_64 set to ensure everyone is ready.
Apologies if you hit this. The modern versions are a lot more robust.
-
A nice little usability improvement coming in the next version of bob: you can specify a dewey pattern for commands that accepts a package match, e.g.:
$ ./target/debug/bob history -o pkgname,outcome,duration 'nodejs>22<26'
PKGNAME OUTCOME DURATION
nodejs-24.15.0 failed 6m34s
nodejs-22.22.2 success 53m39sIf it's not a dewey pattern then it'll fall back to the usual regular expression matching.
Makes it easier to be specific, especially in required pkg lists.
-
A nice little usability improvement coming in the next version of bob: you can specify a dewey pattern for commands that accepts a package match, e.g.:
$ ./target/debug/bob history -o pkgname,outcome,duration 'nodejs>22<26'
PKGNAME OUTCOME DURATION
nodejs-24.15.0 failed 6m34s
nodejs-22.22.2 success 53m39sIf it's not a dewey pattern then it'll fall back to the usual regular expression matching.
Makes it easier to be specific, especially in required pkg lists.
-
@alephoto85 could you be more specific about pkgin slowness? I've done a huge amount of performance work on it over the last few years (e.g. https://federate.me.uk/@jperkin/110900896074569984) and would be curious to know what's left on the table as I've not been able to find much. #pkgsrc #pkgin
-
@alephoto85 could you be more specific about pkgin slowness? I've done a huge amount of performance work on it over the last few years (e.g. https://federate.me.uk/@jperkin/110900896074569984) and would be curious to know what's left on the table as I've not been able to find much. #pkgsrc #pkgin
-
Some binary packages missing for #NetBSD #pkgsrc ... but i suspect it is a work in progress.
https://github.com/NetBSD/pkgsrc/issues/182 -
Some binary packages missing for #NetBSD #pkgsrc ... but i suspect it is a work in progress.
https://github.com/NetBSD/pkgsrc/issues/182 -
Early next week I'll be updating the SmartOS trunk package sets to be built on 20250612, as per announcement to smartos-discuss:
This also migrates them over to bob, and an improved build host configuration that will result in much faster and more reliable builds.
No need to do anything other than ensure you're running at least 20250612 (we release every 2 weeks with new features and security fixes, why wouldn't you?!) and "pkgin upgrade".
-
Early next week I'll be updating the SmartOS trunk package sets to be built on 20250612, as per announcement to smartos-discuss:
This also migrates them over to bob, and an improved build host configuration that will result in much faster and more reliable builds.
No need to do anything other than ensure you're running at least 20250612 (we release every 2 weeks with new features and security fixes, why wouldn't you?!) and "pkgin upgrade".
-
@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
-
@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
-
@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.
-
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.
-
@leaf A cleaner way to handle that would be to add 'only = { exists = "/usr/X11R7" }' to that line, feel free to to raise an issue for this and I can ship this in the default config if it's useful.
-
@leaf A cleaner way to handle that would be to add 'only = { exists = "/usr/X11R7" }' to that line, feel free to to raise an issue for this and I can ship this in the default config if it's useful.
-
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#L152Of course if you need to build X11 apps, install X11 on your host and keep the line.
-
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#L152Of 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...
-
Updated #NetBSD #pkgsrc 2026Q2 binary package counts! Everything seems happy so far.
11.0: aarch64eb 25137 (+1524)
11.0: alpha 798 (+766)
11.0: earmv4 6035 (+51)
11.0: m68k 13308 (+903)
11.0: powerpc 17525 (+881)
11.0: riscv64 18753 (+377)
11.0: sh3el 9079 (+269)
11.0: sparc64 415 (+192)
11.0: vax 6772 (+12) -
Updated #NetBSD #pkgsrc 2026Q2 binary package counts! Everything seems happy so far.
11.0: aarch64eb 25137 (+1524)
11.0: alpha 798 (+766)
11.0: earmv4 6035 (+51)
11.0: m68k 13308 (+903)
11.0: powerpc 17525 (+881)
11.0: riscv64 18753 (+377)
11.0: sh3el 9079 (+269)
11.0: sparc64 415 (+192)
11.0: vax 6772 (+12) -
Aw crap. Upgraded #NetBSD #pkgsrc to 2026-Q2. And now #samba doesn't work. Claims for all directories I want to export that it "does not exist or permission denied" and "Error was Bad file descriptor". It is 4.24 updated from 4.23, with the old configuration. That will take a while to figure out. Maybe some chroot or something, since it cannot even access "/tmp".
Re-installed the old version now, and it works again, so the problem is not with any of the dependencies. -
Aw crap. Upgraded #NetBSD #pkgsrc to 2026-Q2. And now #samba doesn't work. Claims for all directories I want to export that it "does not exist or permission denied" and "Error was Bad file descriptor". It is 4.24 updated from 4.23, with the old configuration. That will take a while to figure out. Maybe some chroot or something, since it cannot even access "/tmp".:thinking_rotate:
Re-installed the old version now, and it works again, so the problem is not with any of the dependencies. -
@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 🙂
-
@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 🙂
-
✅ 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
