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.
Haskell packages every other day…
I hope you auditted all of these for backdoors before installing them
Sorry, where is the backdoor? This is all official arch repos, and nothing even appears sketchy.
Well they are volunteers, something could have slipped up
Highly unlikely, I assume you are nervous after the xz backdoor, but that is almost one of a kind. I couldn’t find any other examples of something like that happening.
We still live in an innocent age
6.5 gigs. “Proceed with installation? y/n”
Yeah, I guess. Fark getting any work done today.
I’m sorry, I gotta - you have the menu on AND the button bar? like, why? you click on those things? you got your screen real-estate on a sale, what?
Be nice, can’t you see they’re only able to afford red pixels?
Ya I turn those off too haha. Hide the scrollbar too… Then press F11. Terminal man…
Both of them combined only take about 1 inch of vertical space, so it’s not that big in real life.
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
oh, of course, sorry if I came off harsh. it’s just, I escaped Gnome’s gigantic title bars and useless buttons in it occupying like half the screen, and couldn’t wait to turn it all off in Konsole, so I’m kinda baffled with anyone having them on. just FYI, check out the keyboard shortcuts for Konsole and you’ll boost your productivity considerably.
edit: this one’s mine. there are many like it but this one’s mine.
Keyboard shortcuts mean memorising. Some people have issues with memory. On-screen buttons mean no memorising.
That’s the cool thing about Linux. You can customise it to your own needs and desires. Everybody is different.
Sorry I just realised I was wrong and I did not have the menu bar by default. I don’t really notice it anymore…
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.
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 don’t think this is true. The package manager is there for a reason to prevent that. If you have more updates to install at a time, then the chances are the same as if you would have installed the problematic update one at a time. Just read the manual intervention information from Arch and see if there is something to do, then it won’t bork. If people don’t know what they are doing and do not read the additional information (that is required to do so on Arch), well yes, then you could end up borking your machine. But not because so many updates are installed at a time. The package manager and operating system and their maintainer designed it in a way that you can install ton of updates at a time without borking. This is fine.
Between this comment about arch and the other comment about opensuse, it must only be apt which has issues with large updates with complicated dependency chains. I remember 5-6 years ago Ubuntu borking itself when I tried to update after a decent gap and had 100+ packages to update. There is also the fact that people used to advice me to make a clean install in lieu of updating whenever a new version of Ubuntu dropped.
Before my switch, i used Ubuntu exclusively for 13 years in row. I always heard of problems (and not at least because of the PPA repositories) when upgrading from one major version to the next, be it a LTS or not. I never did that and always installed fresh because of these stories. Mostly 4 years in between, or sometimes 2.
Its entirely possible that most problems happened because of packages from PPA that the user did not change for the new upgrade. Because PPA repositories were often designed for a specific version of Ubuntu. So its not entirely the fault of the
aptpackage manager in that case.No, it’s just that Ubuntu never correctly upgrades between releases.
I’ve tried so many times, and it basically always failed.
As an anecdote (and not statistics) I have distro upgraded OpenSUSE with 5000 packages to install (thanks TeXlive LaTeX). It was fine.
It’s arch. There’ll be no issue here.
I have yet to break anything doing release upgrades on Debian since… 7? Or 6?
Those are rookie numbers.
Nah, just update it.
This is why I Dont use rolling release Distros on Pcs i wont use often.
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.
Sure, and that’s exactly what you want if you are on a rolling release, isn’t it? If you neglect the rolling release for a month, what did you expect would happen? Also if you have more apps and packages, the more updates will come out. Rolling releases are for people who maintain the system and care about the updates.
What if my pc breaks down or I cannot use it for a month or smth.
On servers and pcs I don’t use often yeah its fairRead the manual intervention notes from Arch that could be important. And do the update. That’s normal and nothing to worrry about, if you know what you are doing.
I’d guess the updates would be about the same on a stable distro, this was a very cluttered install.
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.
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.
My problem with EndeavourOS is that it is terminal centered. I prefer GUI. Don’t think it has a package manager gui.
Isn’t it running plain KDE? If so, Discover is included.
Discover is not working properly on Arch based distros because there’s no packagekit backend for them.
That’s disappointing, Discover is pretty neat.
Well Arch and the like tend to managed from the terminal so I guess no one cared enough to write one.
You can install Octopi or Pamac which both handle the standard repositories and the aur. I don’t know if they handle flatpak or snap though.
I believe I tried Pamac in a VM and it didn’t work properly. Or it didn’t exist in the repôs. I might check it out again if I have time.
It’s in the aur, so use yay or another aur helper to install it
Used tumbleweed for ages. No issues. Switched to slowroll again with no issues. Now trying fedora. All with Kde plasma.
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.
Got busy and didn’t update my template for awhile. Machines would be instantiated a few minors back. 9.2 vs 9.4, for instance, but this was back in 7-land.
Updates would be about 600 packages, or most of the install.
Took 5 min, completely safe. Patch, bounce because we looked funny at dbus so it can’t cope, and then good to go.
I used to tease my windows peer: he’d be still on “do not turn off your computer”.
Is it Debian Sid?
arch linux, i’m sshed from my debian machine.
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
aptoutput.EDIT Nope, that’s
pacmanoutput, seems like they ssh’d into another arch-machine.
