From 3.4.10 already significant pacman key issue existing, forcing us to skip signature verification for many of the packages. Now 3.5.5 makes the situation more frustrating.
- linux-neptune-61-headers still not being migrating from jupiter-main to -rel
- virtualbox-host-dkms build requires libguile-2.2.so.1 while the installed Guile is already 3.0.7
- base-devel even forcing downgrade for most of the packages, corrupting sudo
Well Steam OS is not designed for usage besides gaming so it is nothing to be complained here, but if you rely on pacman heavily like me, better to skip this version and wait for improvement.
Note: to rollback, use Option + Power to select previous OS, then run command ‘sudo rauc status mark-active booted’ as this post.
I also had a LOT of Pacman problems, but I found that for it to work properly on the Deck, i had to populate two keys instead of just one.
sudo pacman-key --populate archlinux
sudo pacman-key --populate holo
After doing that it started working properly and I could install Pacman packages.
Youre a goddamn savior, thank you so much
i was having key issues, but i deleted the cache and re-initialized. no errors after.
rm -R /etc/pacman.d/gnupg
pacman-key --init
pacman-key --populate
okay if I understand we can downgrade the previous and retain the old version. But, if we want to update we just check for update on gaming mode. Is that so?
How do you even use pacman? From my experience every single update overwrites whole system image, and all the packages I installed vanish, as if they were never there. I even had to compile standalone version of Midnight Commander for it to survive updates. Maybe I’m doing something wrong or missing some extra steps to prevent this behavior?
A quick update. Issue is solved by updating to 3.5.7 stable, and changing all the repo in /etc/pacman.conf from ‘rel’ to ‘main’, e.g., [holo-rel] to [holo-main].
Actually 3.5.5 also worked, but need to manually download linux-neptune-61-headers for kernel 6.1.52-valve7-1.