This bug is integration hell. apt was doing what's supposed to do, the control file for libudev1 was doing what was supposed to do, the repository for staged releases was doing what was supposed to do. When each tried to do what they were supposed to do, they found themselves that nothing worked. This is an example that if systems work as they are designed to do, the interaction of those systems isn't guaranteed to work that well. This kind of things are hard to foresee. Heck, the test case literally sets up an entire repository with a 601 packages and their dependencies to make sure that stuff works as intended. Computers are complicated YO!
Announcement
Collapse
No announcement yet.
An Ubuntu 22.04 LTS Fix Is Coming For A Very Annoying & Serious APT Problem
Collapse
X
-
-
Originally posted by braiam View PostThis bug is integration hell. apt was doing what's supposed to do, the control file for libudev1 was doing what was supposed to do, the repository for staged releases was doing what was supposed to do. When each tried to do what they were supposed to do, they found themselves that nothing worked. This is an example that if systems work as they are designed to do, the interaction of those systems isn't guaranteed to work that well. This kind of things are hard to foresee. Heck, the test case literally sets up an entire repository with a 601 packages and their dependencies to make sure that stuff works as intended. Computers are complicated YO!
- Likes 3
Comment
-
One of the best days in my life was when I first installed Manjaro. I was very upset about how many years I just spent fixing different "something went wrong" Ubuntu issues. Two years since then I am still running that same Manjaro install that survived two hardware changes, one SSD migration and numerous attempts to break it like compiling my own kernel, mesa and millions of other things. I never managed to get Ubuntu running for so long even in near-default configuration.
- Likes 2
Comment
-
Originally posted by Sin2x View Post
Yep, and this is exactly what we have QA for. A concept that Canonical, apparently, deems obsolete.
- Likes 4
Comment
-
Originally posted by braiam View Post
No QA would have got this. This is literally end to end testing which is very expensive and no company would set that up for small processes like this.
I was quite puzzled at first what was going on with how a simple apt install was leading to such a broken system but difficult to debug with the process being scripted/automated for the testing and when going to check on the system to find the Ubuntu desktop rebooted and just at the console and without networking support, etc. That was happening on several systems across multiple clean installs
- Likes 3
Comment
-
Originally posted by braiam View Post
No QA would have got this. This is literally end to end testing which is very expensive and no company would set that up for small processes like this.
Test cases are written by developers and they often target very specific circumstances and/or they start with states that are "clean". The whole point of QA is to have people that do really weird shit with your software which is not immediately obvious in an attempt to break your software.Last edited by mdedetrich; 14 July 2022, 01:26 PM.
- Likes 3
Comment
-
So hang on.
Michael doesn't bother to update the system after doing a clean install? And if you actually *do* do that, this bug doesn't manifest?
What the hell is there to complain about then? The first thing you should be doing after installing the system, and especially before installing new packages, is updating everything. Sure, it's weird behavior, but it wouldn't be encountered if only people did the right thing (TM).
- Likes 6
Comment
Comment