Control: severity -1 wishlist On Wed, 2022-09-28 at 13:53 -0400, Zack Weinberg wrote: > On Wed, Sep 28, 2022, at 1:47 PM, Ansgar wrote: > > No, you would need to atomically replace the *entire* system, not just > > individual directories. > > ??? Atomic replacement of each affected directory is, as far as I can see, > both necessary and sufficient to prevent the system being rendered unbootable. > > > But please explain how this is specifc to usrmerge and not many other > > packages. > > As I already said, this code needs to be extra robust because it is being run > from a postinst script, at some unpredictable moment in the middle of an > upgrade to bookworm (in most cases).
You _said_ it, but you really didn't explain it. Let's ask again: why should this be any different than any other package that can bork a system if it crashes just at the right time, of which there are many? Given there's no rationale nor explanation, let's downgrade for now. -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
