And yet I’ve never had an apt upgrade break my whole system.
Define ‘Break’… /j
Unable to boot after the update. That’s happened to me multiple times with pacman, so I eventually switched to Fedora.
Jokes on you, this happened to me on fedora with an nvidia gpu.
You must be very lucky then. I’ve seen it happen so many times.
deleted by creator
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
Been using Arch since 2019, that has never happened to me. Apparently it’s all about the device behind the keyboard, not about pacman. 🤣
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
yas an option to uppercaseSalready exists to update the database,--noconfirmexists to continue without user confirmation.Pacman has the worst CLI flags I’ve ever seen.
Zypper gang, dup!!
[an hour later]
Done!(But actually I like it.)
sudo nix-rebuild switch
uhm, akshually it’s
sudo nixos-rebuild switch --upgradenix flake update nix flake check --no-build git commit -a nh os switchIs 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.
Lots of useful stuff here. Taking all of it.
Does
nhusefast-nix-build(or whatever the fancy nix builder CLI is called) to build your system?I honestly don’t know how nh works under the hood, but it does seem to do concurrent builds, so it’s probably something like that.
This is the way.
Actually
nixos-rebuild switch --sudo.
--noconfirmguix upgrade$ doas apk -U upgradeAnd 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)
That’s because you have to use
apt, not apt-get. Yes, there is a difference
I don’t see much of a difference between the two. That’s why now I’m uninstalling everything I use everyday and put them back as “portable” variants - downloaded as tarballs from their sites, github, or downloaded from Arch’s archive. Already did that with Telegram, Pinta and the browser, soon Audacious will meet the same fate cuz for some reason it uses GTK2, not GTK3 as it should. Plus, having them as tarballs means I can have better versions than those in mint’s repo.
Too bad that pacman can’t be used on Mint, that would be awesome!
topgrade --no-retry --cleanup --yesUsing 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.
pkcon updateDid you decide to use that instead of the normal distro package manager or is there a distro which actually only has
pkconfor the CLI?Nah, I just wanted to toss it in. I kinda want to get used to it, but I always fall back to the native managers.
But I was pleasantly surprised by pkcon (through Discover) being able to do proper system updates on OpenSUSE Tumbleweed. It used to be discouraged to use it for system updates.
Ah, fair enough. Yeah, I kind of have the same problem that I forget about it. I have to use Ubuntu at work and APT is confusing in many ways, so I keep meaning to try
pkconinstead, but I still have to do so…
Or the superior and succinct
parusudo nala upgrade
