Cool!
There’s a behavior with the repos which I’m not sure is intentional or not:
so my repo listing is in the following order:
[cachyos-testing-v3]
[cachyos-core-v3]
[cachyos-extra-v3]
[cachyos-community-v3]
[cachyos-v3]
[cachyos-testing]
[cachyos-core]
[cachyos-extra]
[cachyos-community]
[cachyos]
[core-testing]
[extra-testing]
[core]
[extra]
[chaotic-aur]
[linuxkernels]
What I thought the expected behavior would be, based on past Arch based updates is a “waterfall” where the highest versions takes priority across repos. My ordered list above reflects the repos where the normal updates would occur in. I noticed the following after your reply:
Currently installed:
$ pacman -Q | grep -E "mesa|vulkan|llvm"
libva-mesa-driver 23.1.0-2
llvm-libs 15.0.7-7
mesa 23.1.0-2
mesa-vdpau 23.1.0-2
vulkan-icd-loader 1.3.245-1.1
vulkan-radeon 23.1.0-2
When I run an update with that repo order after an “-Syy” update:
$ pacman -Su
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change
cachyos-testing-v3/llvm-libs 15.0.7-7 16.0.3-1 10.32 MiB
But, if I change the repo order to prioritize [cachyos-v3] over the other [cachyos-*-v3]:
resolving dependencies...
looking for conflicting packages...
Package (4) Old Version New Version Net Change Download Size
cachyos-v3/libva-mesa-driver 23.1.0-2 23.1.1-1 0.00 MiB 4.58 MiB
cachyos-v3/mesa 23.1.0-2 23.1.1-1 0.01 MiB 23.73 MiB
cachyos-v3/mesa-vdpau 23.1.0-2 23.1.1-1 0.00 MiB 4.27 MiB
cachyos-v3/vulkan-radeon 23.1.0-2 23.1.1-1 0.00 MiB 2.79 MiB
After doing an “-Si $item”, the testing-v3 repo has the previous version of the mesa stuff, and the cachyos-v3 repo has the newer version, but pacman is not doing the “waterfall” and picking up the latest versions. Is there additional logic that I’m missing ?
And yes, the various 2.3.1.1 mesa related stuff does NOT work with llvm-libs-16.0.3.