That's because you have to use
apt
, not apt-get. Yes, there is a difference
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!
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
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.
That's happened like once in the last 3 years and the notice was right in pacman before you accepted.
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
Debian users:
What do you mean by PPA?
Also: apt-get
is intended as low-level APT interface for scripts, just use apt
instead. I get why people are confused nowadays, because APT documentation is terrible.
Also you usually do update before upgrade, not after
apt-get
is intended as low-level APT interface for scripts
Ah, that's what they call it now.
I wonder to what they degraded dpkg then?
Isn't dpkg just the program that installs DEB files, without handling dependency resolution?
Yes, apt and apt-* use it.
Why -Syyu and not -Syu?
You ... you understand pacman cli switches?
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.
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
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.
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.
guix upgrade
Zypper gang, dup!!
[an hour later]
Done!
(But actually I like it.)
guix pull . . . . guix upgrade
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.
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.
--noconfirm
God this is the one thing I just hate about Ubuntu. I just avoid ppas now
topgrade --no-retry --cleanup --yes
$ doas apk -U upgrade