Timeline for major upgrades/changes

Now that EOS/Arch has upgraded their main kernel to v5.15, I have a general question regarding major upgrades/changes. Coming from Linux Mint, I’m used to very slow changes - kernel, python, etc.

How long before EOS upgrades their core python packages to v3.10?
How long before the LTS kernel moves to v5.15?

we do use the same package repository as archlinux, and as the nature of a rolling release updates coming in one by one… there is no release cycle.


I should have rephrased the question to How long after a major package is released before EOS upgrades to it? Since I’ve never gone through a kernel/python change before I was curious how long it would take.

Instantly, EOS repos are only for a very few support packages. As @joekamprad said…

1 Like

While I understand that Arch controls almost all of the EOS software base, I thought it would be easier to ask this question here instead of the Arch forums, considering that it will affect everyone when these changes happen.

I withdraw the question.

When Arch updates it’s packages Endeavour does exactly the same at the same time. It runs off the Arch repos apart from the Endeavour addons.

With a rolling release there is no timeline, it continually “rolls”. Unlike Windows or MacOS or Mint or whatever. Just update via Pacman and you are up to date. Reinstalling is not needed.

1 Like

to give the last info … EndeavourOS is not holding back updates, as it is mainly a preconfigured/setup arch-system (indeed not arch only 99,999%)

If you want to check if stuff like kernel or python gets a major version update you can have a look into testing repositories on arch… as they are going there just before reaching the main repos.
p.e. :

1 Like

I think you still have not received a satisfactory answer to these concerns. The answer is very soon after their official release. A few days, maybe a week, it depends on the package really. Sometime it happens the very same day the new version of a particular package is officially announced.

1 Like

Thank you for that. I was more concerned about python, which seems like a much more involved change. Since v3.10 has been out for a while, I had figured Arch would have upgraded by now.

Again, coming from a Linux Mint background, this is something totally new for me.

1 Like

Arch gets updates sooner than most other distros. It’s certainly one of the fastest rolling distros, if not the fastest. Since EndeavourOS uses the same repositories as Arch, it too gets the updates at the same time.

Arch has four official stable repositories: core, extra, community, and multilib, and five testing/unstable repositories: testing, community-testing, multilib-testing, gnome-unstable, kde-unstable.

You can see what packages (and what versions) are in each repository on this webpage:


core contains the most important of packages, things like kernels, bootloaders, as well as important make/build dependencies, like the GNU Compiler Collection. The package python is in the core repository, as well.

Now, it is an Arch Linux rule that all updates to the packages in the core repository have to go through the testing repository first. Because of that, packages in the core repository tend to be a bit slower to update, typically it takes at least a week after the upstream release, often a bit more. The reason for this should be clear: if a broken update is pushed to the core repository, the result could potentially be catastrophic: thousands of broken Arch systems.

The version 3.10 of Python is not even in the testing repository yet. Once it gets there, you know that it will probably appear in the core in a week or so, unless issues are found. It could possibly take even a bit longer for Python, since so many other packages depend on it.


This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.