You must log in or register to comment.
As someone who works on Windows daily… this is so true. One of the things that really annoys me with Windows is being able to reliably do updates. Running any of the update stuff, seems more like a suggestion and if Windows deems your request worthy, it might SLOWLY do something.
In Windows it would be
winget upgrade -all
I’m pretty sure.
Winget update --all
But yes, this updates any packages distributed by Ms store and winget repos. As an IT professional, I love winget.
Winget is a step in the right direction… but man it is SO SLOW. If PowerBI Desktop has an update, it is actually taking me 20+ minutes to update a handful of apps.
Which will try to update all 3 apps that are available via winget. It will break one of them. It has 50% chance of bonking some drivers.
More than 3 apps. https://winget.run/
But Window’s software incompatibility doesn’t change anything.
Then windows says “Undoing Changes” because its shit software doesn’t work
Didn’t know we were still doing apt-get
I have a lot to learn
iirc, apt-get is the version to use in scripts. They keep the input & output consistent so that it won’t break things.
Regular old apt is for humans to use at the command prompt, and that’s what I use all the time.
How is apt better for humans?
Yeah why do I still see this everywhere
haven’t used linux in decades but used to use aptitude over apt-get
KDE Plasma recommends applying updates at reboot like Windows for stability. In fact, that is how it does them by default
Wait, plasma does your system updates? I don’t think it’s an appropriate chain of commands
Discover is integrated with the rest of Plasma, so if you run your upgrades via Discover on Plasma, it’ll use Plasma settings. The same goes if you update with the little button in Plasma’s taskbar
KDE Plasma does what I tell it to
Sure, what I’m saying is the “windows way” of applying updates isn’t bad and there’s a reason why they do it
Bah!!
Feels aggressive sometimes
And what he’s saying is it’s his life. It’s now or never. No one’s gonna live forever. He just wants to live while he’s alive. It’s. His. Life!
Someone who gets it 🥲
jesse, what the fuck are you talking about
Aaaand… you’re on Debian, so Blender 4.0 just got added to the testing branch. (Blender 4.0 still haven’t been tested for 168 hours of continuous running without touching it)
It’s a good thing system packages (which should follow a conservative update approach if possible to guarantee system stability, unless hardware demands newer packages) and user applications (which you’d usually want to be most up-to-date) are increasingly isolated from each other and mostly able to follow their own schedules. Also improves security and such.
topgrade -yYou’re welcome.
genini update my machine
Because I’m apparently a raging masochist
sorry, usage of this tool has been discontinued, please use [WORSE TOOL WITH DIFFERENT NAME]
(joking but not really, gemini-cli is going to the google graveyard, replaced by antigravity-cli that’s basically the same, but in google’s tradition it launches with less features and also it’s not FOSS)
nixos-rebuild switch
going to nix from another distro like the leap from going from windows to linux
I’d rather switch back to Windows than try NixOS again. The immutable structure was far too rigid for me.
I run an Ubuntu server and I make the history keep a lot of entries so I remember which files I changed
It shouldn’t have to be like this
Every single time I’ve run upgrade on Debian, I’ve bricked my install. I’m sure I’m doing something wrong 😆
I’m probably a big newb, but on my headless Debian machines, major updates screw me up sometimes too.
- “Ah! All my updates can’t be found on the server? Oh we’re done with “Bo-Peep” and moving to “PotatoHead” now? Maybe I should be on the newsletter or something…”
- Change some sources in that one text file I gotta look up every time…
apt update && apt dist-upgrade“Oh, that’s a lot of errors…”
I’m sure it’s not that bad and I’m being dramatic but I do kinda appreciate my rolling OpenSUSE Tumbleweed for this reason lol. I feel like newbies would struggle with that major release upgrade process…
Watch out! People in here looove Debian for some reason
Yeah, you better watch what you say; Debian Gang got eyes on you.
I love Debian ha!
Haha Debian is really cool and I’m glad it’s there! Definitely rock solid! Don’t wanna throw any shade at their very important work. :)
…I’m just too goofy to update it properly sometimes. 😅 Skill issue lol.
Ironically I had numerous discussions with people claiming updates often break rolling distros like Arch, and I’m in the same boat as you - only ever had issues with major upgrades on Debian
You misspelled
pacman -SyuNo, you misspelled
zypper dup. But with enough time, you’ll get there.That’s a corporate propaganda that I can’t stand for
I kneel
The only true answer
Update before upgrade you nonce
Isn’t this how Non-Torvalds Linus bricked his install
C’mon, it’s Debian! Obsolete anyway. Update today, upgrade in a week, not like things gonna change. Perhaps the man forgot the upgrade a week ago, upgraded, and then decided to double-check there’s nothing new anyway. Right?
No, no. You gotta update last to let them marinate for a while before you upgrade. If you upgrade too fast it just doesn’t taste the same.
Yay
paru
Update first, then upgrade
It runs so much faster if you do upgrade first \s
Good catch. Haven’t been using apt in some time.
sudo pacman -Syuparuyaywhich yay yay: aliased to paru
Is it even
apt-getstill? thought they changed over toaptlong ago andapt-getis just a symlink for legacy reasons.At least that’s what I last read… (speaking as someone also loving candy) .
apt is a wrapper over the apt- binaries (apt-search apt-cache etc).
aptis meant more for user interaction andapt-getis more stable and more for scripting. Butapt-getis often used in online tutorials because it doesn’t really change.I think it wasn’t for APT but I once worked for a business with a lot of RHEL, the script that was updating hundreds of servers was using the user wrapper instead of the binaries. A warning was displayed in the script to warn not to use the wrapper for scripts.
I warned my team leader of the issue and was completely ignored and was said that it was an issue for the team that made the script in the first place.
I gave up.
A few weeks later, the poorly designed script botched a major update on hundred of servers because the wrapper had a tiny change and the update script didn’t handle it well.
It’s insane to me how much money a business can waste for stupid shit like that. The devs warned us not to use their wrapper to script on, the linux team did it anyway, my warning was ignored, many hours of engineers work was wasted fixing the chaos that ensued.
Or if you’re me,
yay -Syuand wait 4 fucking hours (Because you barely ever remember to do it).Just
yaywould sufficeI do update my Arch each time it boots. Like a tiny tradition to me.
Doing
yay -Syu --noconfirm & shutdownwhenever I turn my machine off has been the solution for meWait but that means your computer will stay on if the update fails, right?
Wait but that means your computer will stay on if the update fails, right?
If it was
&&then the second command would only run if the first command was successful.But @[email protected] wrote only one
&which instead means the first command will run in the background and the second will execute at the same time… which does not seem like a good idea in this case 😅Oh damn, yeah it was supposed to be &&, probably messed it up when arguing with the stupid phone keyboard adding spaces after symbols
It doesn’t deserve the rest if it fails.
You turn your machine off???
Once a month or so yes!
I kid. I reboot every couple weeks to save myself a bunch of headaches.
I reboot every time an update triggers mkinitcpio. Otherwise som kernel modules stop working.
Thank you!
