Do you forget that you need to update your system?

Rolling release master race checking for updates several times per day.

Cannot update 600 packages because library-you’ve-never-heard-of conflicts with what-the-fuck-even-is-a-polypterodaclib?
- KDE's qt6 transition sure was something
- polypterodaclib
  
  Fucking hell, I nearly spat out my coffee at that one word. Bravo.
- I haven't had those issues on Tumbleweed. It gets massive updates all the time but everything seems to go just fine.
- Whenever something breaks/doesn't feel right, I'll just reinstall the OS and it'll work again
Rolling release, update every now and then, 4000+ packages is common. Nothing ever breaks.

Thanks zipper!
- I'm guessing you mean zypper?
i haven't checked for updates on one of my machines for like 7 months now. some packages are partial upgrades (hilariously, xz is currently on the backdoored version and I don't care to fix it)
the thing survived multiple 500+ package upgrades from partial upgrade state and has been running for like 2.5 years now
emerge --sync?

Update your system frequently,
that minimizes the chance of things breaking in my experience.

I only ever update between projects - no way am I going to break something in the middle of everything.

This time, jump to new gnome means broken extensions as usual, and a hilarious one: qbittorrent doesn't show it's window in Wayland (gnome-with-X works). The soft is running, it there in the list of apps, there's even a big X "Close Window" button on Zoom Out but no actual window.

Eh. Lol?
- I only ever update between projects - no way am I going to break something in the middle of everything.
  
  I learned to do that the hard way...
But not too frequently. Updating too often on Arch will increase your chances of something breaking. Updating once a week or twice a week gives the developers some time to fix bugs and make changes to other packages as needed
- Your comment is my reasoning why I use Manjaro :P
  
  All the Arch niceness,
  with fewer bugs / breakage
  and easier to use.
  
  Sure you might get an issue from outdated dependencies from AUR packages from time to time, but the chance / impact of those is usually rather small.

Once I went travelling and left my arch(btw) desktop computer unplugged for just over a full month.

When I came back there were 1 235 packages needing updating, between repo and AUR.

.... It worked fine tho. That install didn't really go to shit until about a month ago, when months of sloppy system management on my end finally caught up to me and left me with a lot of mysterious issues. So I cut my losses and ditched it.

I'm using OpenSUSE Tumbleweed now (btw).

I'm using OpenSUSE Tumbleweed now (btw).

I wonder why people don't say : I don't use Arch BTW.. ?
skill issue
- Yeah, I ran Arch for years and every time the wiki or someone in irc said, "Do it X way, not Y," I always followed that instruction. Never had a single issue with system stability.
  
  Guess that's atypical? I learned a lot, these days I mostly use Ubuntu or Debian.
  
  Tbh, trusting pacman with everything and keeping my AUR pkg sources preserved in a source folder is literally all it took to keep the system stable. Idk, is that a lot? It felt easy.
I'm using OpenSUSE Tumbleweed now (btw).

Well, prepare for some even bigger updates. When a new libc or gcc or similar such version comes out, they like to recompile everything.
Sometimes you get 4000+ package updates, just from one day to the next.

They do that, though, because it increases compatibility, and you get automatic snapshots, too, so it's kind of less daunting than 250+ package updates on Debian et al.
- I haven't personally had those huge updates ever break on Tumbleweed. The one thing that apparently caused stuff to break was the recent KDE 6 update, but I've heard so and did it with Discover's offline update and it all went fine.
Tumbleweed rebuild the entire repo after the xz-utils thing, I had like 5500 to update

My roommate will have 400+ updates waiting because "something breaks every time I update."

My roommate will have 400+ updates waiting because “something breaks every time I update.”

Sounds like your roomie uses Ubuntu with a bunch of random PPAs.

Use glorious nixos. Never fear anything breaking. And even if you manage to do so just roll back in the boot menu or terminal.

Ahh until something hangs when updating grub. Had it happen twice over the last couple of months. No real biggie as it's not the hardest thing to recover from / easy enough to pull my config and rebuild.

Maybe it's me, maybe it's Nixos or Grub.
- Why would you update grub?
  
  Also I am not sure if I am even using grub. Does systemd have a bootloader?
  
  Normal people don't change their bootloader that often.
- That's why I use Gentoo. If something breaks I just boot system from external drive and solve the issue. Or even if bootloader breaks I can use kernel from external drive, but boot into main system.

I have a laptop running Linux Mint I only use for hosting bar trivia. I only need it to run like 4 applications but I need them to run flawlessly. The last time I updated it jacked up my soundboard, which I didn't notice until I was in front of a crowd and it played the wrong sound effects. Never again.

Laughs in NixOS, smiles in btrfs snapshots.

Btrfs snapshots not always work tho), i tell this story for *th time on lemmy but my fedora 38 btrfs broke completely from update to 39 and when i tried revert to 38 with help of btrfs snapshots, what came out is weird mix of 38 and 39 and when i reverted again, my whole ssd on which fedora btrfs was installed, this ssd locked completely, on hardware level, even though it was brand new, 2 weeks of usage by me, i fortunately repaired ssd myself and flashed lmde6 on it, but avoided btrfs and fedora after that
- Yeah, also a bit wary of btrfs. I sure hope some day bcachefs can be the true cow filesystem in Linux. There is hope, it is pretty good already.
  
  NixOS definitely solves the issue of rollbacks the best here. And FreeBSD.
Was using btrfs then in manjaro, broke my laptop because btrfs seems to be shit at handling loss of power cases. Switched to good ol ext4 and nixos, never looked back since.

it didn't break anything "so far"

Don't worry. When you reboot, your kernel will have magically disappeared!

Spell it with me D-E-B-I-A-N

Just wait till you have 1200+ packages to upgrade. Luckily OpenSuSe Tumbleweed handles it like a champ

Just wait till you have 1200+ packages to upgrade. Luckily OpenSuSe Tumbleweed handles it like a champ

New major version of GCC? Let's recompile everything! Takes a bit to download but yes, openQA at openSUSE does its job.

Or something not working, so you ignore the issue and update around it until the updates allow it to be fixed.

Me after updating 39 packages and therefore killing my audio:

I update my packages every day on debian. I have yet to have something break. The only issue I ever had was steam got uninstalled when dist-upgrading from debian 11 to 12. Promptly reinstalled, of course all my games were still on disk.

Updating pandoc on arch feels like 250 packages, so you don't have to forget updating for this experience.

I once updated shortly before pandoc got updated, and I have the habit of running yay again so it says that no packages need updating. On this occasion however, I suddenly had more updates than before

Its gentoo it broke everythihg because portage is for galazy brain people

Soooo many man pages

I'm on the Ubuntu 24.04 beta and this is what I get in a day.

Only for version updates. Beyond that, dnf-automatic handles those invisibly in the background. I only notice them when Firefox gets an update and demands a relaunch before it lets me keep browsing.

Laughs in atomic.

But also yes...

I have had 750+ after not using my laptop for a couple weeks lol, and like 30 flatpack updates.

Funnily enough, flatpack took longer.