Step forward with an advice offer proposal

diff --git a/914897_merged_usr/ballot.md b/914897_merged_usr/ballot.md
index 089950d5a8b08227b47a04c7374c576d4c891c86..3f03916cd7947658213df6dc82a064a617f3eadc 100644 (file)
--- a/914897_merged_usr/ballot.md
+++ b/914897_merged_usr/ballot.md
@@ -77,18 +77,18 @@ It can be summarized by the following table:
 |      all |       no        |        yes        |        yes       |        no       |        yes        |         yes         |           no         |
 ```
 
-## Immediate actions
-
-Given that hosts with different top-level directory schemes already exist; there are various ways forward that would allow for Debian to converge to a desireable situation:
-
-* Flag-day to get all hosts on "merged `/usr`", through a base-files version; probably in buster+1 (bullseye)
-* Disallow "merged `/usr`", leave users who already have merged `/usr` in an unsupported situation
-* Let Debian converge to a situation where non-"merged `/usr`" Debian hosts are equivalent to symlinked "merged `/usr`" hosts; do this through upgrading all packages shipping files outside of /usr (but exceptions) to stop doing this. Could be achieved by setting policy for buster+1 (should) and buster+2 (must), or maybe even shorter. This would make the symlink "shortcut" migration redundant.
-* Support both "merged `/usr`" and non-"merged `/usr`" systems forever: this implies that our packaging tools need to either support countering effects of "merged `/usr`" (e.g. through manipulating PATH for builds to detect files only in their .deb paths) or identifying tainted packages, and letting installing users decide (warn or error out at install time).
-
-Given the tests from the reproducible builds' initiative, it does not seem impossible to enforce that official Debian packages support being built on either "merged `/usr`" or non-"merged `/usr`" systems; however, due to Debian being upstream to many other distributions, and due to `.deb` packages (which often don't go through the same level of checking and policing as official Debian's) being built by Independent Software Vendors (ISVs), our users will probably face similar problems to what we have described.
-
-It's bizarre to have official buildds be non-"merged `/usr`" while user hosts will converge to be more and more "merged `/usr`".
+The current state of buster is `weak`.
+
+== TO BE DISCUSSED
+== ## Offering Advice §6.1.5
+== 
+== Given that:
+== * hosts with both directory schemes already exist,
+== * it seems unpractical to allow official packages to be built on either directory schemes,
+== * there's inherent value in the simplicity of "merged `/usr`" directory schemes,
+== 
+== the Technical Committee considers that the desireable solution at the time of bullseye is `hard`.
+== TO BE DISCUSSED
 
 ## For buster