On Sat, Nov 22, 2025 at 5:35 PM Assen Totin via Infrastructure
<infra(a)lists.almalinux.org> wrote:
>
> Hello, and apologies if I ended up in the wrong place.
>
> We're updating some Alma-10 instances from the "10" repo (not the "10.0" and not the "10.1" repo) - which, at least as per the GUI repo browser on https://repo.almalinux.org/almalinux is a symlink. We want to be on a rolling release where the repo we update from automatically switches from one point release to the next when the next point release becomes available.
>
> We are aware of the recent mess around upstream and downstream releases, for example, in EPEL-10 - but there we use the "10z" repo, which follows the RHEL-10 rolling release (because their "10" repo is, apparently, aligned with CentOS).
>
> Our expectation is that since Alma-10 has "10", "10.0" and "10.1" with "10" been a symlink, this symlink will be switched from 10.0 to 10.1 when 10.1 launches; however, two weeks later I don't see any 10.1 packages when I browse the "10" repo (e.g., I expect to see kernel-* packages for 6.12.0-124.8.1.el10_1), so it seems "10" still points to "10.0" (which does not make much sense to me at the moment).
>
> So, my question is, will this switch of the target for "10" happen and when? And if not (i.e it points to 10.0 till EOL?), how to we stay on a rolling Alma-10 version without the need to change the minor number on each VM we have every 6 months?
>
AlmaLinux OS 10.1 has not been released yet, which is why it hasn't
switched yet. The final release of AlmaLinux OS 10.1 should be
arriving soon, though.
That said, based on what you said, you might want to consider
AlmaLinux OS Kitten[1] instead. You'll get the latest content released
continually (you'll be on the beginnings of what will be AlmaLinux OS
10.2 right now!) and EPEL is equally supported on Kitten, as CentOS
Stream (the direct upstream for AlmaLinux Kitten) is tracked as the
primary target for EPEL 10.
I personally use AlmaLinux Kitten for all of my AlmaLinux deployments. :)
[1]: https://wiki.almalinux.org/development/almalinux-os-kitten-10.html
Hopefully that helps!
--
Neal Gompa (ALA: ngompa)
Hello, and apologies if I ended up in the wrong place.
We're updating some Alma-10 instances from the "10" repo (not the "10.0" and not the "10.1" repo) - which, at least as per the GUI repo browser on https://repo.almalinux.org/almalinux is a symlink. We want to be on a rolling release where the repo we update from automatically switches from one point release to the next when the next point release becomes available.
We are aware of the recent mess around upstream and downstream releases, for example, in EPEL-10 - but there we use the "10z" repo, which follows the RHEL-10 rolling release (because their "10" repo is, apparently, aligned with CentOS).
Our expectation is that since Alma-10 has "10", "10.0" and "10.1" with "10" been a symlink, this symlink will be switched from 10.0 to 10.1 when 10.1 launches; however, two weeks later I don't see any 10.1 packages when I browse the "10" repo (e.g., I expect to see kernel-* packages for 6.12.0-124.8.1.el10_1), so it seems "10" still points to "10.0" (which does not make much sense to me at the moment).
So, my question is, will this switch of the target for "10" happen and when? And if not (i.e it points to 10.0 till EOL?), how to we stay on a rolling Alma-10 version without the need to change the minor number on each VM we have every 6 months?
Thanks you in advance for your help,
Assen Totin
