After the bug with pop_os that happened to Linus I stopped using it. I’d like reliable system and clearly the pop_os team doesn’t know how to package their software if a dependency error that bad happens
They commented on their video that it was their fault. There was never a packaging issue. The issue was that we pushed a systemd source package update to Launchpad, which silently didn’t build or publish the 32-bit systemd library packages, because Ubuntu had systemd on a blacklist for 32-bit package builds. We noticed this minutes after packages were published, and had it fixed within an hour later.
This didn’t actually affect any systems in the wild because apt held back the update until we had worked around the restriction on Launchpad (there was an invisible ceiling to the package version number). They were only affected during that time period because they manually entered that sentence from the prompt in a terminal. We stopped using Launchpad with 21.10, so all packages released since then are the same packages that are built and tested by our packaging server, and used by our QA team internally.
The drama and reputational damage that LTT caused was unnecessary. Especially given that they uploaded this video a week later, and never attempted to reach out. They still have yet to properly edit the video.
That vid is actually good, it exposes lots of issues that regular users run into when switching to linux, in fact debian changed apt to make it harder to remove essential packages like linus did.
On Arch to remove essential package you will not be prompted with confirmation to remove them, you will have to add --nodeps --nodeps twice to the command to be able to do so, no idea how long this has been the case on arch or if it was implemented after linus vid as well, but that is something that should have been that way a decades ago, I still see on reddit posts of people that accidentally delete grub or remove important directories from their system.
After the bug with pop_os that happened to Linus I stopped using it. I’d like reliable system and clearly the pop_os team doesn’t know how to package their software if a dependency error that bad happens
They commented on their video that it was their fault. There was never a packaging issue. The issue was that we pushed a systemd source package update to Launchpad, which silently didn’t build or publish the 32-bit systemd library packages, because Ubuntu had systemd on a blacklist for 32-bit package builds. We noticed this minutes after packages were published, and had it fixed within an hour later.
This didn’t actually affect any systems in the wild because apt held back the update until we had worked around the restriction on Launchpad (there was an invisible ceiling to the package version number). They were only affected during that time period because they manually entered that sentence from the prompt in a terminal. We stopped using Launchpad with 21.10, so all packages released since then are the same packages that are built and tested by our packaging server, and used by our QA team internally.
The drama and reputational damage that LTT caused was unnecessary. Especially given that they uploaded this video a week later, and never attempted to reach out. They still have yet to properly edit the video.
Linus as I Linus tech tips? Imagine giving a removed about that scummy ass clown.
That vid is actually good, it exposes lots of issues that regular users run into when switching to linux, in fact debian changed apt to make it harder to remove essential packages like linus did.
On Arch to remove essential package you will not be prompted with confirmation to remove them, you will have to add --nodeps --nodeps twice to the command to be able to do so, no idea how long this has been the case on arch or if it was implemented after linus vid as well, but that is something that should have been that way a decades ago, I still see on reddit posts of people that accidentally delete grub or remove important directories from their system.