The next step is for me to design how to present the repair option, so I have a few questions.
1. When this happens, whose fault is it? Can a power cut during installation cause a broken package, for example? Can a badly-coded package cause it? What other causes are there? 1a. If a badly-coded package can cause the problem, would an automated repair ever fix that kind of problem? 2. Is the statement "You have to repair this before you can install or remove any further software" actually true? 2a. If so, is it reasonable to follow the same approach as for a broken apt cache <https://wiki.ubuntu.com/SoftwareCenter#broken-catalog> -- let people browse without nagging them, but don't let them install or remove stuff without doing the repair first? 3. About how often would the repair process succeed? 100% of the time? 90%? 50%? 4. About how long would the repair typically take? Ten seconds? A minute? Ten minutes? 5. About how often would the repair involve removing stuff, and how often would it involve installing new stuff? 5a. If it does involve installing new stuff, can we tell ahead of time whether any of that new stuff needs to be downloaded from the Internet (and therefore requires an Internet connection)? Thanks. -- Can't fix broken packages from within USC https://bugs.launchpad.net/bugs/442262 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
