I am currently on Manjaro 25.0.7 with Plasma 6.3.6 and i can’t find anything regarding the release of Plasma 6.4 in stable branch.
Does someone know when this should happen?
I am currently on Manjaro 25.0.7 with Plasma 6.3.6 and i can’t find anything regarding the release of Plasma 6.4 in stable branch.
Does someone know when this should happen?
As usual, it will come when it is ready, if it is not in Stable there are probably still some things that need to be worked on. Check thread for Testing and Unstable branch for information.
Because Manjaro is a rolling release distro there is never any concept of a release target date - when things are considered ready they become available.
Well, it hasn’t reached Testing branch yet, and may even be completely skipped over in favour of Plasma 6.5:
You can check which version of Plasma each branch is currently on here: Branch compare for Manjaro - plasma-desktop
If you need Plasma 6.4 urgently, you can easily switch to Unstable branch:
To switch to Unstable branch:
sudo pacman-mirrors --api --set-branch unstable
After you changed the branch, rebuild the mirrorlist and update your packages:
sudo pacman-mirrors --continent && sudo pacman -Syu
This was asked a few times already and Philip explained it eventually. It may be a surprising answer, at least it was for me because i assumed Manjaro to be a rolling release. And reading the Wiki about differences to Arch it read like testing would be a snapshot of unstable which for the recent testing snapshots had meant something like Plasma 6.4.3. However as Philip explained it is not so simple. Rather we have a Zetar point release and that features certain Plasma and Gnome versions - XFCE doesn’t make much difference they don’t change for years
Two steam-rollers following fresh and Unstable Arch… when we had problems with Plasma a while back, I went from the stable one to the unstable, hit a few bumps, fell back to Testing and then went back to Stable and just waited until it was deemed ready.
In truth they’re all ‘unstable’… but unless you’re running it on your router, ‘stable’ is rather overrated. Since those dodgy Plasma days, I’ve been sitting on Testing - and that’s been pretty much rock solid.
In that particular case, syncing of database needs to be forced:
sudo pacman-mirrors --continent && sudo pacman -Syyu
Let’s get this straight:
Manjaro isn’t a normal rolling release. Manjaro is a curated rolling release, meaning there’s an extra layer of testing to make sure you, me, us get stable software.
It’s even on the website:
Robust with Rolling Releases
Experience a combination of the latest software for your enjoyment, your development, your creation needs, and well-tested updates.
We follow an approach of cascading stability to let you pick the version of Manjaro that fits your needs.
For the benefit of those who might prefer the commandline with pamac
;
pamac update --no-aur --force-refresh
which is the pamac
equivalent of;
sudo pacman -Syyu
Both effectively perform the same task.
A reminder to passers-by that under normal circumstances only a single y is required and/or recommended when using the pacman
command to perform an update.
Off-topic:-
I also use Plasma on BSD and just recently upgraded to Plasma 6.44. While I haven’t had time yet to test it fully (try to break it) I note that there are a few nondescript issues that no doubt translate to other OS as well.
While it may take some time for Manjaro to call it stable enough for GA, it should be well worth the wait.
sudo pacman -Syyu
Sorry if my brain is a bit slow. Does it mean the instruction for switching back isn’t correct since it says
Going back to the stable branch is easy. All you have to do is to repeat the above, and use stable as the branch value.
where “repeat the above” refers to set the branch to stable and execute
user $ sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syu
Sorry if my brain is a bit slow. Does it mean the instruction for switching back isn’t correct since it says
Perhaps you just need your morning/evening coffee/tea.
The instructions for switching branches are correct.
The focus of the previous few comments from @heyjo (who was adding to a previous comment) and myself were only focused on refreshing the mirrors;
So, sudo pacman -Syyu
or pamac update --no-aur --force-refresh
as opposed the sudo pacman -Syu
that @scotty65 had mentioned:
After you changed the branch, rebuild the mirrorlist and update your packages:
sudo pacman-mirrors --continent && sudo pacman -Syu
I should add that in practice sudo pacman -Syu
will be fine in this context, but if it isn’t, add the additional y.
Regards.