Perhaps the dist-upgrade process could acquire some kind of exclusive lock early (and release late) such that it could guarantee that the packaging infrastructure wouldn't be in use by another process (or fail early, rather than midstream, if the packaging infrastructure is in use).
If only there were a way to early invoke dpkg (to create its usual lock), leave it running, send signals to that process to invoke substeps of the whole operation, and eventually release the process and its lock near the end of the upgrade. I have a very naive view of the system, so that's as deep as my recommendation can go, but I hope it provides at least a hint of inspiration. I certainly understand the challenge with having a "all or nothing" update to a system platform. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413762 Title: precise -> trusty upgrade failed dpkg status database is locked by another process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1413762/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
