I think switching branches wiki needs an improvement

I think switching branches wiki needs an improvement: Switching Branches - Manjaro

Trying to switch from stable rn and tried like 10 mirrors, all leading to the following:

error: failed to prepare transaction (could not satisfy dependencies)
:: installing pacman (6.1.0-7) breaks dependency 'libalpm.so=13-64' required by libpamac
:: installing pacman (6.1.0-7) breaks dependency 'pacman<6.1' required by pacutils

Ignoring this leads to a borked system (partial-upgrade, broken python etc)

So yeah

-sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syu 
+sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syyuu
1 Like

IMHO a better solution would have been to temporarily uninstall the conflicts.

sudo pacman -R libpamac pacutils
sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syu
sudo pacman -S libpamac pacutils

IMHO your IMHO stinks.

Read the ‘ignoring this leads to a borked system’ again.

The problem is yy is needed to force a refresh.

1 Like

IDK what you think, rly. :wink:

Anyways, I’ve been told, multiple times actually, that the double-y is a Bad Idea :tm: and also when switching branches. I think it was @cscs that mentioned it the last time. Apparently it also causes a lot of strain on the server(s).

The double yy only force a db refresh.

1 Like

I think that your brilliant idea is what I tried first and have the receipts to prove it. Which means I had to restore from a snapshot.

That is why I want to prevent your misinformation from spreading, lest you want to support newbies recovering from a partial upgrade yourself

Thanks @nikgnomic, but I’m done commenting. I’ve had too much different opinions from too many people about this. I’m sticking to doing things my way.

:smiley:

1 Like
  • -yy
    does refresh the database (which seems necessary when switching branches)
  • -uu
    does allow downgrades (which seems sometimes necessary when switching branches)

So this seems right to me.

I’m still waiting for further contributions, but I’m ready to change this in the wiki.

:footprints:

1 Like

Don’t be too dogmatic on this. This comes from arch, and they have unlike manjaros 3 branches, only one repo (yes,they have testing, but that’s only for development).
So, when doing usual updates -Syu is fine, thus recomended.
When swithing branches, one should force database refresh.
cheers

1 Like

OP is switching from Stable branch so downgrade is not necessary

Manjaro Wiki recommends use of downgrade option after switching back to Stable branch
How do I go back after changing to one of the testing branches

A famous bon mot asserts that opinions are like a–e-holes, in that everyone has one. There is great wisdom in this… but I would add that opinions differ significantly from a–e-holes, in that yours should be constantly and thoroughly examined.

We must think critically, and not just about the ideas of others. Be hard on your beliefs. Take them out onto the verandah and beat them with a cricket bat… Be intellectually rigorous. Identify your biases, your prejudices, your privilege.”

― Tim Minchin

3 Likes

Do you happen to have yay-bin (or another package) installed from AUR that happens to include pacman-6.1.x among its dependencies?

This scenario created issues for several users very recently.

pacman 6.1.0-7 on Testing branch - Provides: libalpm.so=14-64

libpamac 11.6.4+1+g3fe0f42-1 on Testing branch - Depends On: libalpm.so=14

pacutils 0.14.0-1 on Testing branch - Depends On: pacman

The fastest mirrors might not have up-to-date packages for Testing branch

Check Manjaro Repository - Status of mirrors or:

pacman-mirrors

I am pretty sure in 2 things: one should not install critical system components like pacman or libpamac from aur or git;
And switching branches should be done with refresh. For the sake of simplicity i vote for Syyuu in the wiki. Uu does not hurt when not applied and the new users have to learn only one command for all 9 possible cases.

1 Like

You have the same issue as someone using out of sync mirrors recently

I vote for “read manual and use some brain”. Or better automate everything for Manjaro users. :joy:

2 Likes

yy forces db refresh
uu allows downgrades

When changing branches ~UP~ (Stable → Testing) neither should be needed.

When switching ~DOWN~ (Testing → Stable) uu is not required, but can be used if one wants to sync with Stable and downgrade the packages. But I repeat this is not required, and may not even be desirable.

IMHO the wonkiness OP describes is because of their sync status and unsupported packages in the first place.

2 Likes

Still seems like force refresh is required when switching branches – at least sometimes. Just had the same thread maybe a week ago.

EDIT:

It’s this one Trouble switching to testing branch

1 Like

I vaguely remember something similar … but if I recall these were examples of people who otherwise use pamac … and pamac needs something like ‘force-refresh’ from time to time, even if you dont switch branches. But thats another subject.

EDIT for your EDIT.

Without any confirmation … I might tend to agree with the other comment there.
Did the OP switch branches and then sync right after? Or sort mirrors after changes branches?
Because sorting mirrors should be done. And probably would have removed the need for the double y.

(and itself may not have been required if the mirror/sync status was in perfect order beforehand)

Could be. But still, what “sorting”? You change branches so you pull from different url. But apparently you half-do it. Someone should probably write some libalpm overlay. :stuck_out_tongue:

To switch to the testing branch from stable I use this command:

sudo pacman-mirrors -aS testing

To switch to stable:

sudo pacman-mirrors -aS stable