there’s a world of options. this is an LTS distro. use Arch or Nix or whatever if you want the latest packages. i actually switched to NixOS because the CUDA drivers were too new on Arch, and i wanted a better way to pin versions.
or i dunno keep publicly complaining about it until someone does the work for you
It would be nice, but the time it takes to do the work of validating package versions for LTS candidacy is either limited or not free, so this is the acceptable compromise.
i guess it would be nice, but packages being a few months out of date is pretty normal for Ubuntu, in my experience. i’m not sure what their testing process is like, but part of using something like Ubuntu is stability guarantees. if they felt like the couldn’t do that for newer versions for whatever reason (resource constraints, lack of downstream interest from stakeholders, etc) they’re not necessarily obligated to.
I’d love to hear what your solution would be? They freeze everything two months out to allow for thorough testing and unless your answer to the problem is switching to a rolling release cycle (which is exactly the opposite of what its supposed to be), then I don’t think there’s anything to be done
This sort of distro is and always has prioritised stability over having the latest of everything and that’s a good thing. I use CachyOS on my desktop but it’s the absolute last thing I’d put on a server, let alone a production one.
It was about 4 months out of date at code freeze from my understanding and 6 months out of date on release which is honestly better than I’d expect normally for packages in official repos
there’s a world of options. this is an LTS distro. use Arch or Nix or whatever if you want the latest packages. i actually switched to NixOS because the CUDA drivers were too new on Arch, and i wanted a better way to pin versions.
or i dunno keep publicly complaining about it until someone does the work for you
I mean, even in an LTS distro, it sure would be nice if the packages were reasonably up-to-date on the day the version was released.
It would be nice, but the time it takes to do the work of validating package versions for LTS candidacy is either limited or not free, so this is the acceptable compromise.
i guess it would be nice, but packages being a few months out of date is pretty normal for Ubuntu, in my experience. i’m not sure what their testing process is like, but part of using something like Ubuntu is stability guarantees. if they felt like the couldn’t do that for newer versions for whatever reason (resource constraints, lack of downstream interest from stakeholders, etc) they’re not necessarily obligated to.
2 months. lts or not, ubuntu’s freeze date is and has historically been about two months before release.
if the 2 year cycle between lts is too long for someone, they don’t have to stay on that ride.
26.04 is brand new
it’s Ubuntu dawg. you get what you pay for.
…and you pay more for other distros?
just a silly turn of phrase meaning: you should know that this is what you signed up for
I didn’t pay? Even if I did you got the same result, 🤣
It’s brand new so they have no excuse for having such an old package version.
I’d love to hear what your solution would be? They freeze everything two months out to allow for thorough testing and unless your answer to the problem is switching to a rolling release cycle (which is exactly the opposite of what its supposed to be), then I don’t think there’s anything to be done
This sort of distro is and always has prioritised stability over having the latest of everything and that’s a good thing. I use CachyOS on my desktop but it’s the absolute last thing I’d put on a server, let alone a production one.
Just use Docker if you need something newer
I’m very familiar with their freezing schedule. The impression I’d gotten from this thread was that the package was much more out of date.
It was about 4 months out of date at code freeze from my understanding and 6 months out of date on release which is honestly better than I’d expect normally for packages in official repos