I have a "theory" :)
The announcement is for #pkgsrc source code. It takes about 2 or 3 weeks for things to replicate and binaries to be built.
I have a "theory" :)
The announcement is for #pkgsrc source code. It takes about 2 or 3 weeks for things to replicate and binaries to be built.
All right, pkgsrc 2025Q1 has just been announced on the mailing lists.
It's not even on pkgsrc.org yet!
Experiences with #dreckly / #pkgsrc on obscure Unixes:
#UnixWare - bootstrap succeeded! Just needed a few simple fixes.
#OpenServer - see UnixWare.
#BSDOS - kernel panic during installation. Support incomplete.
#HPUX - kernel panic during installation.
#QNX - bootstrap success! No changes needed.
#Haiku - bootstrap failed due to open() behaviour. "Invalid argument".
If you have a shell on an #IRIX or #HPUX machine, please let me know!
As I have said, I am not an expert, so #pkgsrc people here may well disagree with me.
@bentsukun ? Any ideas for Joel?
Question to #pkgsrc people in the context of #slackware #linux usage. I have bootstrapped pkgsrc with ˋbootstrap --prefer-pkgsrc yes --prefer-native openssl`. Everything compiles and works well so far.
Trying to build thunar, I get unsolvable error with a dependency. So I added "samba gvfs" to the prefer-native variable in my mk.conf.
But the build process still tries to compile samba4 and gvfs packages. What am I doing wrong?
@netbsd will participate to Google Summer of Code 2025!
Would you like to contribute to NetBSD and/or pkgsrc in the next months?
Please check <https://blog.NetBSD.org/tnf/entry/gsoc2025_tnf> for more info!
#pkgsrc is now on Go 1.24 as the default Go version!
This time around, I found zero breakage in any of our Go software, which is a first.
System Administration
Week 4, Package Management
In this video, we continue our discussion of the difference between the operating system and so-called "add-on software". We conclude that in order to install and maintain all such software, we want to use a package manager, and illustrate common features by example of the 'dpkg', 'rpm', and #NetBSD's #pkgsrc tools.
What does "pbulk-resolve: Invalid input" mean?
#pkgsrc
Just painlessly enabled #PQC on my website. My #NetBSD VPS is still on 9.1, so has an old #OpenSSL in base. #pkgsrc to the rescue!
cd /usr/pkgsrc/security/oqs-provider
make install
cd ../../www/apache24
make PREFER_PKGSRC=openssl replace
Update /usr/pkg/etc/openssl/openssl.cnf; then add to apache's ssl.conf:
SSLOpenSSLConfCmd Curves X25519:X25519MLKEM768:SecP256r1MLKEM768:secp384r1
Restart apache, verify via
openssl s_client -groups X25519MLKEM768 -connect
It has unfortunately come to the point where I need to seriously evaluate my involvement in the #pkgsrc project.
I'm spending literally all of my time fixing regressions, and the tree keeps getting worse. It's clear that the project no longer has any interest in anything other than #NetBSD.
I need to decide whether to keep on with this incredibly demoralising work, or just fork.
If anyone else is interested in a stable, portable, non-"Move Fast and Break Things" version of pkgsrc let me know.
Stupid post-lunch thought: #Slackware #Linux extended using #pkgsrc ️
One of these days either #pkgsrc will stop including upstream changelogs in commit messages, or #GitHub will finally provide repositories with an option to disable auto-closing of issues.
Today is not that day, so I'm left to go around reopening a bunch of issues, yet again.
Software engineering in 2025.
@thomholwerda There are #pkgsrc devs hanging out on the Fediverse too