On debian, I never worry - most of my regular use computers are that.
Maybe hesitant about a dist-upgrade, but i backup all my home and main edited config , and apt-list regularly anyway.
on my arch that i use regularly I never worry.
on steam deck never worry - kind of obviously.
On my arch system that i only use occasionally i just expect trouble whenever i go back to it after a too long (say 2 months i’d be edgy)…
I always run my backup procedure first - i have to anyway to sync my home folders.
update archlinux-keyring first as that’s the most common issue .
if any dependency issue emerges that cant be fixed by removing one or two packages or using pacman-static - i normally just go straight back to live usb and chroot, or be prepared to reformat and jump back to the pacstrap part of install process and reinstall base system.
On debian, I never worry - most of my regular use computers are that. Maybe hesitant about a dist-upgrade, but i backup all my home and main edited config , and apt-list regularly anyway.
on my arch that i use regularly I never worry.
on steam deck never worry - kind of obviously.
On my arch system that i only use occasionally i just expect trouble whenever i go back to it after a too long (say 2 months i’d be edgy)…
I always run my backup procedure first - i have to anyway to sync my home folders.
update archlinux-keyring first as that’s the most common issue .
if any dependency issue emerges that cant be fixed by removing one or two packages or using pacman-static - i normally just go straight back to live usb and chroot, or be prepared to reformat and jump back to the pacstrap part of install process and reinstall base system.