APT 2.3.12 package manager released, will no longer let you break everything

Quoting: Nevertheless

Quoting: slaapliedje

Quoting: AussieEevee

Quoting: ObsidianBlkThose neon warning signs are there,

I think part of the problem was that there was no neon warning signs. The only warnings Linus got was an error from popshop that wasn't clear on what was happening... and a giant wall of text from apt.

That 'wall of text' ends with "you are about to remove essential packages, type exactly, 'Yes, I know what I'm doing' to continue."

Which is more than enough to say 'stop, you're about to do something horrendous to your system.' I have made many jokes before about not being able to do flashing red text in Confluence because of people not following the wiki... But really there are two things to blame here. 1) Linus being smart enough to be dangerous. 2) Linus not being patient enough to read the warning.

Since Linux distros wait for more users coming over from the Windows realm, package managers should expect users coming that have been trained to ignore most of the text that is beeing thrown at them during installation of software. For them it is almost unthinkable that the installation of a gaming software could uninstall parts of their OS.
So I think it's an improvement that such users now actively have to search for the command that can do harm, instead of being able to use it by just ignoring something.
I would love the error message being clickable (depending on the kind of error of course), linking the user to a site where he/she can read about and report problems and solutions with the package that led to the error.

I say there are 2 issues here:
The first one 100% apt/Pop OS fault and that is that this should NEVER have happened during simple package installation, even if done from terminal.

But.. as anyone who worked with computers for a long time knows.. One of those things that should NEVER happen will eventually happen. Doesn't matter if you are on Linux, Mac or Windows. Which brings me to the second issue.

The second issue is 50% user fault and 50% Windows fault for training its users to be dumb and not read Warnings (yes even if it's a simple installation of package, user should be expected to read Warnings and Errors).

So instead of package managers having to expect that their users will not read Warnings (which imo is ridiculous), I would say that the distros aimed at new users like Mint and Pop should include a message when running the Terminal (with the option to disable the message for future) that the Terminal is a high level tool and the user is expected to read and understand potential Warnings.

Trying to install Steam shouldn't have caused this problem in the first place, but the terminal was also pretty clear, in my view, that you (Linus) should not do what you are about to do. I don't blame APT here.

Quoting: Purple Library Guy"Potentially harmful" doesn't really sound that bad. It also sounds vague, like the kind of message you get when the computer doesn't really know just what you're doing or whether it's actually going to do anything important, but is just putting in the boilerplate because the command generally has the potential to do serious things. Especially if you come from the Windows world, where I think the OS bitches every time you do anything other than browse the web with Microsoft Edge . . .

The more I read responses like this the more I think it was intentional. There's no way no one else has had this problem in years but a famous and technically knowleadgeable youtuber doing a live test session.

To use the terminal you need to read, it's a requirement. There's no NEXT button in the terminal, and anyone blindly copying and pasting text into the terminal and foolishly using the Intro key as a NEXT button in a Windows installer is doomed. If this is a bug, we should put an agreement request before the terminal opens to free the devs from responsibility, but then the user wouldn't read it neither. Looking at this like a bug it's unsolvable.

If you read "Potentially harmful" after a long text, and you have to type "Yes, do as I say", and after having tried and failed to install a package in the standard way, you should be wary that something worth of attention is happening. You just have to read a few more lines above to better understand what's happening or stop if you have no clue. But the messages were clear even for the newest users that could read. And thinking otherwise is really believing that Linus is an idiot, that he's not.


Last edited by berarma on 19 November 2021 at 6:47 pm UTC

Quoting: berarma

Quoting: Purple Library Guy"Potentially harmful" doesn't really sound that bad. It also sounds vague, like the kind of message you get when the computer doesn't really know just what you're doing or whether it's actually going to do anything important, but is just putting in the boilerplate because the command generally has the potential to do serious things. Especially if you come from the Windows world, where I think the OS bitches every time you do anything other than browse the web with Microsoft Edge . . .

The more I read responses like this the more I think it was intentional. There's no way no one else has had this problem in years but a famous and technically knowleadgeable youtuber doing a live test session.

To use the terminal you need to read, it's a requirement. There's no NEXT button in the terminal, and anyone blindly copying and pasting text into the terminal and foolishly using the Intro key as a NEXT button in a Windows installer is doomed. If this is a bug, we should put an agreement request before the terminal opens to free the devs from responsibility, but then the user wouldn't read it neither. Looking at this like a bug it's unsolvable.

If you read "Potentially harmful" after a long text, and you have to type "Yes, do as I say", and after having tried and failed to install a package in the standard way, you should be wary that something worth of attention is happening. You just have to read a few more lines above to better understand what's happening or stop if you have no clue. But the messages were clear even for the newest users that could read. And thinking otherwise is really believing that Linus is an idiot, that he's not.

Well there are the possibility that it was done deliberately to drive a thesis (Linux is difficult) and I accused Linus of such when it happened. But there is also the possibility that Linus was simply blinded by his Linux prejudice (you have to use the terminal in Linux to get anything done and the terminal is this magic obscure box).

That said, I think that many people in this thread should see this small clip from LTT that they released yesterday: https://www.youtube.com/watch?v=_XHoNYJZPb4 where they start to discuss that Windows is far from perfect and that they perhaps should have a part 6 where they try to approach a new Windows install as a noob and not as a hardened Windows veteran.

But what struck me as extremely funny from that clip is that Linus and Luke have earlier complained en masse on how Linux users always reply "well works for me" when they try to describe a problem that they have, and here the instant that Linus mentions that Windows is not perfect he gets a "well it works for me" type of reply in the chat that he reads out loud without really reflecting that this signifies that it's not Linux users that have the "it works for me", its computer people at large. Also the comment section is full of "it works for me" regarding Windows update, completely hilarious how oblivious the Windows users who earlier where so salty about Linux are about their own behaviour when Windows gets a tiny bit of scrutiny.

Quoting: damarrinLinux and apt have been fine before they came along and breaking one's system is part of the learning experience and now there will be people who will be denied that.

Oh no! How awful! They won't get to break their systems?! How could we deprive those poor people?

Here's a camp I am almost in: A computer is an appliance. I don't want a "learning experience" where I try to use my microwave oven and break it, I don't want it with my computer either.

Obviously, there are quite a few people, especially current Linux users, that that statement really doesn't work for. It doesn't apply to how they use, think about and work with computers.
But it's not wrong either, and I think some computer people need to be a little less purist and romantic about how their particular interest is the one that everyone in the world has to learn about.

Quoting: RoosterSo instead of package managers having to expect that their users will not read Warnings (which imo is ridiculous), I would say that the distros aimed at new users like Mint and Pop should include a message when running the Terminal (with the option to disable the message for future) that the Terminal is a high level tool and the user is expected to read and understand potential Warnings.

So for people who don't read warnings, what you want is a warning, because that will surely make them read warnings.

Quoting: berarma

Quoting: Purple Library Guy"Potentially harmful" doesn't really sound that bad. It also sounds vague, like the kind of message you get when the computer doesn't really know just what you're doing or whether it's actually going to do anything important, but is just putting in the boilerplate because the command generally has the potential to do serious things. Especially if you come from the Windows world, where I think the OS bitches every time you do anything other than browse the web with Microsoft Edge . . .

The more I read responses like this the more I think it was intentional. There's no way no one else has had this problem in years but a famous and technically knowleadgeable youtuber doing a live test session.

Oh, come on. We know about this particular happening because it was a famous youtuber doing a live test session. Who knows how many trees fell in the forest but nobody was making a video of them?

But it was also a somewhat freak occurrence--the package failed in such a way that doing a perfectly normal command was going to cause this (if you were somewhat overconfident in your approach). That is not normal, but non-normal things happen and this one did. The package really was that way, this was acknowledged. What do you figure, Linus bribed the packagers or the Pop!OS people to screw up the package so it would cause that error?

I know that there are flatpaks and other "sandbox" concept, but why is the core installation sharing "ressources/files/libs/whatever" with optionnal components (post install softwares)... How come installing Steam may mess with basic components from the DE? I mean, couldn't they be 2 separate things, isolated from one another (ex: different copies of the same files)? I'm just wondering and I'm no software engineer. I'm totally aware that it's probably much easier to say than do.

Quoting: Nevertheless

Quoting: slaapliedje

Quoting: AussieEevee

Quoting: ObsidianBlkThose neon warning signs are there,

I think part of the problem was that there was no neon warning signs. The only warnings Linus got was an error from popshop that wasn't clear on what was happening... and a giant wall of text from apt.

That 'wall of text' ends with "you are about to remove essential packages, type exactly, 'Yes, I know what I'm doing' to continue."

Which is more than enough to say 'stop, you're about to do something horrendous to your system.' I have made many jokes before about not being able to do flashing red text in Confluence because of people not following the wiki... But really there are two things to blame here. 1) Linus being smart enough to be dangerous. 2) Linus not being patient enough to read the warning.

Since Linux distros wait for more users coming over from the Windows realm, package managers should expect users coming that have been trained to ignore most of the text that is beeing thrown at them during installation of software. For them it is almost unthinkable that the installation of a gaming software could uninstall parts of their OS.
So I think it's an improvement that such users now actively have to search for the command that can do harm, instead of being able to use it by just ignoring something.
I would love the error message being clickable (depending on the kind of error of course), linking the user to a site where he/she can read about and report problems and solutions with the package that led to the error.

Terminals typically have clickable links. So inserting that into apt would not be a terrible idea. "Your package installation causes some conflicts which may render your system unusable. Click here $(link) for more details."

Quoting: MohandevirI know that there are flatpaks and other "sandbox" concept, but why is the core installation sharing "ressources/files/libs/whatever" with optionnal components (post install softwares)... How come installing Steam may mess with basic components from the DE? I mean, couldn't they be 2 separate things, isolated from one another (ex: different copies of the same files)? I'm just wondering and I'm no software engineer. I'm totally aware that it's probably much easier to say than do.

Complex programs share and reuse a lot of code. Most of that is not written by the same developer, so they have to rely on promises made by the original developers. If the original developers choose to modify their promise, the others using their code will have to adjust their code accordingly, or if possible, choose to use the old version. Proprietary software often follows old versions.

Now the distributions basically take all this code and try to mix it into something useable. This means they will have to pick versions of the shared code (libraries) and the applications that run and match their versions so they work. For proprietary software even this basic thing is impossible, since sharing it is illegal and allegedly makes you a see bandit.

Games and graphical programs are good examples for programs that reuse a lot of code relating to your DE, at the minimum the window manager and the graphical server. (xorg/wayland)

The package manager is set up in a way that it tries to mix and match the versions and the programs so that your system works. If this fails you can encounter such a bug. I don't know if they followed debian yet, but it used to be before the multiarch system the 32 bit libraries were called library-i386. For some reason this used to result in such a headache as in the video. It's also possible the person who made the steam package made an error.
You can already do such sandboxing, you can run every application in it's own vm for example, on cubes.


Last edited by dvd on 19 November 2021 at 11:41 pm UTC