Andy, where are you? Please post that you are ok or what issues you met.
After successful chroot, basically I thought to ask you next:
- Please report what package changes were exactly done:
check the output by yourself:
tail -n 100 /var/log/pacman.log
or change 100 last lines count to another value, but to show the Mesa-git Update issue - #6 by alven action and all further events.
you can copy/paste here full report or auto-submit it and to post a link here:
tail -n 100 /var/log/pacman.log | curl -F'file=@-' https://0x0.st
the server will respond in terminal with short link to the report.
Before to proceed let someone to check that log, if I will be unavailable at that time.
The next planned actions l think will be:
- Let’s restore all as was including
mesa-git package of
22... version and fix for it by Mesa-git Update issue - #10 by megavolt suggestion:
a) switch branch to
sudo pacman-mirrors --api --set-branch unstable --proto https --country Germany
b) do a full upgrade
pamac update --force-refresh --enable-downgrade --aur
c) install that new
mesa-git which you have previously but by that time we already got it’s newer dependency version:
pamac build mesa-git
d) exit from chroot environment
e) reboot PC and boot installed OS copy.
If all is OK, then perhaps you want to switch back to
stable branch of updates, but to leave package versions as currently they are:
sudo pacman-mirrors --api --set-branch stable --proto https --country Germany
and refresh databases (all newer package versions you got will be intact and someday
stable branch will get these newer versions also):
sudo pacman -Syyu
If you have some problems, please post.