Switch from x86-64-v3 to x86-64-v4 #241
Labels
No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ALHP/ALHP.GO#241
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is this really necessary: "If you want to switch between levels, e.g. from x86-64-v3 to x86-64-v4, you need to revert to official packages first, then enable your desired repos again" ?
I was thinking that changing repositories to x86-64-v4 and do a pacman -Suuy would be enough.
Maybe this was explained somewhere but I cannot find the post.
Since the new v4 packages would have the same versions (with some exceptions) as your old v3 packages, you would not really be upgrading anything, even with
uu
, which only allows pacman to do downgrades, which these are not. The only way not to do the revert and upgrade strategy is to explicitly reinstall each package, but that would break the explicit flags on packages (there is a way not to break them, but I wanted to keep this step somewhat simple), if not more.If you just switched repos and did nothing more than a
pacman -Suy
, you would only get newly built versions (after your repo switch) from v4, everything else would stay on v3.OK, understood