On 2025/09/23 22:31, Terry Cocksworth wrote: > Is it really entitlement, though? I've had a look through the Ports- > and Misc lists and it simply isn't the case that people were nagging > about this as soon as some package was a week out of date. Or even a > whole month out of date. But now it's been a year, since Arm64 users > last saw up-to-date packages. Or to put it in a more flattering way, > it's been half a year. For the second year in a row.
This OpenBSD/arm64 user generally has up-to-date packages available. Of course, like many people on this architecture, I'm running -current snapshots not release. New packages there are generally built about twice a week (thanks Peter). Looking at [email protected] reports since 7.7 - not exactly scientific but it's the best data I have - there are 11 from release/stable kernels, 32 from -current snaps. This probably undercounts people running snaps because it's quite common to only send dmesg at release time. For arm64, much of the available hardware is really more suited to development-type machines (where most of us run snapshots) than servers (where releases/stable are more common), so this is not a big surprise. In general the majority of developer resources are focussed on -current because this is what we run ourselves and what we need to be in good shape because it's what makes up the next release. There is also the option of generally running release/-stable but shifting to snapshots closer to the end of the release cycle (where -current is less of a moving target anyway), that's what I usually do on my main (amd64) colo'd personal server. > If providing users with package updates truly is, by your very own > admission and own words, a pain, and that you are on the verge of > giving up on it, maybe you will at least consider asking others > in the project for help. I was the only taker when solene retired from running the packages-stable builds last year. And I need them on amd64 for work anyway so if nobody else took them on I'd be doing my own builds (at least for the packages we're using) there anyway.
