On Sat, 14 Aug 2021 at 14:33:44 +0200, David Kalnischkies wrote: > the current 'transition' plan is to have the > release notes nudge all people who upgrade instead of reinstall their > systems, chroots and what not to please do it for all of them by hand > at a to be specified flag day someday between now and bookworm > freeze
That is certainly not my plan. It might be someone's plan, but it is not one that I would support. I think the earliest flag day that would be possible (for requiring merged /usr, or for completely undoing merged /usr, or for any similarly "big" transitional path) is the bookworm release date. We specifically don't support skipping a release, so the fastest possible timeline for an archive-wide transition goes something like this: 1. during bookworm development: interested people make the transition as robust and graceful as possible; package maintainers must make their packages compatible with the transition (if they have not already) but must not assume that the transition has already taken place 2. bookworm release: systems must transition at or before the upgrade to bookworm (bullseye systems are not required to transition until/unless they are upgraded) 3. during bookworm+1 development (testing/unstable post bookworm): package maintainers may assume the transition has taken place smcv