until a pacman update breaks your system because you didn't read the release notes telling you it needed manual intervention beforehand 🤣
Been using Arch since 2019, that has never happened to me. Apparently it's all about the device behind the keyboard, not about pacman. 🤣
I use informant which in theory fixed this but even then there is an issue on it about some things happening earlier in pacman than the transaction hook it uses so... Bleh. This shit needs to be built into pacman itself, seriously.
Every time there's been need for manual intervention the update just fails, I check the news to do the thing, then update as usual
That's happened like once in the last 3 years and the notice was right in pacman before you accepted.
And yet I’ve never had an apt upgrade break my whole system.
Yeah, maybe I'm just not smart enough but I always have the best luck with Debian/Ubuntu style distros. I'm glad Arch users are happy with Arch, it just doesn't work for me
sudo dpkg --configure -a
my beloved
guix pull . . . . guix upgrade
Why -Syyu and not -Syu?
You ... you understand pacman cli switches?
No, I just hold my y key until there are many many ys.
y?
-Syyyyyyyyyyyyyu
Yes. -Syyu is for "Sync (repository action), database update (forced), upgrade packages", in that order (though the flags don't have to be). Doubling a lowercase character like yy or uu is to force the operation. yy in particular shouldn't be needed, as it only overrides the "is your database recent" check. Unless you're updating more than every 5 minutes, using a single y is perfectly fine.
And that’s why I don’t use PPAs, but you do you, I guess…
Yep. I'm on Debian for many years now. Every broken update I can recall was either caused by an undocumented PPA or nvidia drivers (which have finally been fixed, for my card at least)
This meme brought to you by outdated packages in the official repo
Mfw I get to go through the same yt-dlp steps after a fresh install
guix upgrade
Never had an update break on headless Debian. Even when switching from 12 to 13. That shit is solid.
I'm getting used to arch on my main desktop and I still can't figure out why the hell "sync" is the wording pacman uses for updating or why 'y' is refresh. Sync refresh upgrade my ass. I will admin, it is fast.
Because you’re “sync”ing with the state of the repo. You’re not necessarily upgrading. Sometimes the repos have a lower version than what you have, so you would be downgrading in that case. Or sometimes you’re just using it to install a new package and its dependencies.
-u
is upgrade. And -uu
is upgrade or downgrade. It’s used to filter the packages that sync operates on, so basically you’re syncing any packages that have a different version than the repo.
-y
for refresh? No idea. -r
is root, so I guess it was already in use by the time someone added refresh?
sudo emerge -avuDN world
sudo emerge -avuDUg world
--changed-use, -U:
- Tells emerge to include installed packages where USE flags have changed since installation. This option also implies the --selective option. Unlike --newuse, the --changed-use option does not trigger reinstallation when flags that the user has not enabled are added or removed.
--getbinpkg [ y | n ], -g:
- Using the server and location defined in PORTAGE_BINHOST (see make.conf(5)), portage will download the information from each binary package found and it will use that information to help build the dependency list. This option implies -k. (Use -gK for binary-only merging.)
Yeah, I used to use -U but I prefer -N personally. I like the system to be consistent with what it would be from a fresh build.
sudo nix-rebuild switch
uhm, akshually it's sudo nixos-rebuild switch --upgrade
nix flake update
nix flake check --no-build
git commit -a
nh os switch
Is the routine I've settled into. Flake update because I use flakes, flake check because it's easier to see any warnings about deprecated options and the like so I can fix them preemptively, git commit after the check to avoid back-to back commits where the second is fixing some issue with the first, and nh because I like the pretty dependency graph and progress bar.
Zypper gang, dup!!
[an hour later]
Done!
(But actually I like it.)
Using Debian as my main laptop distro, I am usually an arch user but figured with it being a light weight laptop I wouldn't need arch, its been fine but installing updates can be frustrating, after a few weeks gnomes appstore breaks, then I need to use terminal to apt update, apt --fix-broken install.
Which Debian distribution are you using, stable, testing, unstable?
I take care of a couple machines for family members. Those have Debian stable with automatic update (unattended-upgrade). I can't recall the system or packages ever breaking. At most users are a bit confused when an update change the UI a bit.
Sticking to stable and avoiding third party repos gives a pretty solid system. Only developers or sysadmins might consider Debian testing. Only people working on Debian itself should use unstable.
Fedora: sudo dnf update, type the letter y, done.
I don't understand why apt still has update and upgrade as two separate things.
You can even add the -y flag to skip typing y. Which apparently doesn't work for pacman judging by the command above
Since lowercase y
as an option to uppercase S
already exists to update the database, --noconfirm
exists to continue without user confirmation.
God this is the one thing I just hate about Ubuntu. I just avoid ppas now
why does Ubuntu even use ppas
Of course it won't do anything, you need to update (refresh the index) before you upgrade (download and install updates), silly you
topgrade --no-retry --cleanup --yes
--noconfirm
Memes
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.