not yet. I was doing something last night, so I wasn’t able to update my system. I’m planning to do it right now.
I get this warning as well !!
$ sudo pacman-mirrors -f 5 && sudo pacman -Syyu
Warning: manjaro-hello: Local Version (0.7.0-6) is newer than extra (0.7.0-5)
Edit: I always updated the system as soon updates came out.
so from this link ( in stable )
you should have number version from right
exemple on zstd 1.5.5-1 or you will get 1.5.4-1 from your screen side
it is like you are still using manjaro-mirrors ( from december 22 ), not pamac-mirrors or pacman-mirrors
better is wait return on this point before any action
Does it mean that the update was actually downgrading that package?
And I have a solution. Run your updates
What should I do? If it is something that can be fixed, or just some mirrors need to be corrected, I’m willing to learn what to do.
can you return
pacman -Qs pacman-mirrors pacman -Qs manjaro-mirrors pacman -Qs pamac pacman -Qs pacman
❯ pacman -Qs pacman-mirrors pacman -Qs manjaro-mirrors pacman -Qs pamac pacman -Qs pacman local/pacman-mirrors 4.23.2+2+g2f58b3c-3 Manjaro Linux mirror list for use by pacman local/pacman-mirrors 4.23.2+2+g2f58b3c-3 Manjaro Linux mirror list for use by pacman local/libpamac 11.5.2-3 Library for Pamac package manager based on libalpm local/pamac-cli 10.5.0-2 A Package Manager based on libalpm with AUR and Appstream support local/pamac-gtk 10.5.0-2 A Package Manager based on libalpm with AUR and Appstream support local/pamac-tray-icon-plasma 0.1.2-4 Pamac tray icon for plasma users local/pacman 6.0.2-10 A library-based package manager with dependency support local/pacman-mirrors 4.23.2+2+g2f58b3c-3 Manjaro Linux mirror list for use by pacman local/pkgfile 21-2 a pacman .files metadata explorer local/timeshift-autosnap-manjaro 0.10-1 Timeshift auto-snapshot script which runs before package upgrade using Pacman hook. local/yay 12.0.4-1 Yet another yogurt. Pacman wrapper and AUR helper written in go.
Would be nice and helpful as well to mention the reason about that manjaro-hello version story!
have you go in testing and then try to go back in stable ?
no need to rush , just wait return confirm for mirrors update
You are using pacman and opting to not pass the downgrade flag.
sudo pacman -Syuu
The extra u allows for downgrading to match the mirror.
[Note for some:
pamac are not the same.]
Does it mean I do have to downgrade by
Did the newer manjaro-hello version came by the pamac command? which I did use some days ago for an AUR package update.
if you type pacman -Syu or -Syyu , you have an upgrade
if you type pacman -Syuu you get a downgrade
if you type pacman -Syyuu you get a full synchronize with mirrors ( including revert )
Isn’t the right side the installed version, and the left the version the mirrors are offering? Otherwise there would be no downgrade warning for
manjaro-hello. See the bottom of the list in the opening post.
You dont have to if you dont notice any problems.
But if you want to be in-lign with the mirrors … add an extra u.
Notice the second section under
-u in the manual page for pacman…
... -u, --sysupgrade Upgrades all packages that are out-of-date. Each currently-installed package will be examined and upgraded if a newer package exists. A report of all packages to upgrade will be presented, and the operation will not proceed without user confirmation. Dependencies are automatically resolved at this level and will be installed/upgraded if necessary. Pass this option twice to enable package downgrades; in this case, pacman will select sync packages whose versions do not match with the local versions. This can be useful when the user switches from a testing repository to a stable one. ...
but I still do not understand by which action my manjaro-hello version (0.7.0-6) came from.
I never switched branches, always on stable.
It was pushed to stable, but reverted. Not your fault.
OK, now I got it.
So everyone has to downgrade it.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.