Haven't booted this machine for a month or two... look at these updates!

To be fair, arch could look like that after a few days.

NixOS is like that every day for no reason
- staging rebuild cycles only happen every two weeks or so.
  The reason is always that something changed and causes all dependent packages to change, requiring a rebuild of those too.
- Oh, you updated one byte in your config? Better download the entire ducking Internet and rebuild everything!
It is arch
- It looks like it's Debian's logo in the bottom left and that that's apt output.
  EDIT Nope, that's pacman output, seems like they ssh'd into another arch-machine.

Read the Arch news before clicking "yes".

- I used to be an adventurer like you, but then I took an error to gpg.
I have Informant installed for this. Saved my hide a few times.

people laughed at me for choosing debian. they asked why i chose to have ancient runes running in my computer

who's laughing now?

Still we, dinosaur.🦖
We are still laughing, no worries.
p.s. Debian is great, I am just a "kind of new" void converted.
- went looking for it. "stable rolling release" sounds really interesting, but i'm scared of installing it and being mistaken for a systemd hater
👑

Sometimes I wish someone would make a an Arch box and come back to it years later to see the updates it has missed.

But that's assuming an Arch box would be reliable enough to stay alive that long lol.

Always heard of 20+ year old bsd and debian machines chugging along with no issue.

It won't rise much beyond that, since you only get one update per package. Whether it's upgrading Firefox from version 120 to 121 or to version 130, it doesn't change much in terms of download size, nor the number of updates.
At least, I assume, Arch doesn't do differential updates. On some of the slower-moving distributions, they only make you download the actual changes to the files within the packages. In that case, jumping to 121 vs. 130 would make more of a difference.
If you do want lots of package updates, you need lots of packages. The texlive-full package is always a fun one in that regard...
I have updated arch systems that had not been powered on for years before. It was fine. No issues what so ever. Arch is not some flaky distro that breaks if you look away for a minute. My main system has had had the same install for over 5 years now and I regularly forget to update it for months at a time. Again, no issues.
- Yeah really the biggest issue I could see is pacman’s keyring being so out of date that it has to be manually refreshed with a new one
My arch install has been going strong for about 5 years now
I had that on a physical machine! It broke hardcore lol I had to reinstall the OS after trying to update
Pretty sure you can't leave Arch lying around for even two months.
- Yes, you can. You can even update Arch after a year. But you'll have to do a few more steps than just pacman -Syu

You see, this is why atomic desktops aren't a bad idea.

This has nothing to do with immutable desktops.
- Well in an immutable distro, there is little to no chance for the system to end up in an unusable state (I guess it is the same for distros which apply the updates atomically). Traditional distros are far more likely to bork when so much shit is updated at once

I did this regularly on arch. And it didn't end very well.

So you neglected the operating systems maintained regularly, despite it being a rolling release? I assume you didn't read the manual intervention instructions that are posted regularly too. I don't understand people using a rolling release and then not caring about the maintenance. Off course it won't end very well.
- Well, my life turned to chaos at some point and I had to neglect some things for a while.
- I'm using arch on my desktop for >5 years. Never read those instructions. Sometimes my update looks like OPs. Just hit Y. All fine.

This is why I Dont use rolling release Distros on Pcs i wont use often.

I used to care but with recovery tools being what they are and most apps being containers... my base systems tend to be a little more disposable.
That said, I haven't had problems, even if I am at risk for more of them. I have my snapshots and my backups.
Because you get updates and have an up to date system?
- Because you get a update once a update for a package comes out, If you dont update for a very long time you need to download a very large update.
I'd guess the updates would be about the same on a stable distro, this was a very cluttered install.

Remembers Tumbleweed fondly

Would you recomend it for daily usage?
- I used Tumbleweed for eight years with no problems. I only moved to EndeavourOS because Suse bared their corporate teeth and I got fed up being a couple of generations behind on the Nvidia drivers. EndeavourOS is also good.
- Used tumbleweed for ages. No issues. Switched to slowroll again with no issues. Now trying fedora. All with Kde plasma.

Haskell packages every other day...

Is it Debian Sid?

arch linux, i'm sshed from my debian machine.

And they're red, that means the offer is about to expire. Better act quick!

Better apt quick!

Nah, just update it.

Be nice, can't you see they're only able to afford red pixels?
Both of them combined only take about 1 inch of vertical space, so it's not that big in real life.
Ya I turn those off too haha. Hide the scrollbar too.. Then press F11. Terminal man…
Are you talking about the 2 bars at the top of the window? If yes, I find them more useful than the used space. Probably a matter of taste

You wouldn’t believe the shit I’ve seen on internet connected production servers…

My personal prod systems never have many upgrades... But they're running Debian stable and I have unattended-upgrades installed and configured.

Looks like a !!FUN!! time in Dwarf Fortress.

welp, looks like you don't use python virtualenvs... well i guess jokes on you all your shit is probably broken now (and as a bonus, that's probably a big part of the donwload size as well) :p

Probably should, but this machine is already cluttered terribly. A good bit of the download size is likely Pytorch files.

Those are rookie numbers.

Recently updated a nixos machine that was on the shelf for five years or so. A few options and packages had been renamed, fixed those, upgrade completed with zero problems.

Only issue with this update was a maintainer's keyring had expired and been replaced, so his packages didn't pass the signing check. After re-installing the keyring, the whole think works fine.