On Wed, 08 Feb 2012 13:23:58 -0500, nicolas vigier <[email protected]> wrote:
The problem is the bad update, not that it was allowed without root password. Updates should not hose the system, and that's why there is a policy on no new versions in update when possible, and qa tests.
The main problem I've seen with updates breaking a system happens when there is a large number of updates (such as kde), and the mirror you're updating from synced in the middle of the main repositories being updated. I think the best solution would require the primary repositories to have some sort of a lock, so that they cannot be synced from in the middle of an update, or better yet, some way to have all updates put into a hidden directory, until they have all been loaded, and then have a single operation that puts all of the updates into the active directories without allowing any downstream mirror to sync while that's happening. Regards, Dave Hodgins
