Comment 44 for bug 2002043

Just a few observations before release.

1) The verification for Jammy apparently has a copy-paste error,
as the banner about the env var is present (step 5) _before_ the
package from -proposed -- which adds it -- is installed (step 6).

To be clear, this is not a problem and should not block the release,
as the _new_ behavior (with -proposed installed) is what matters,
and that looks correct in the output:
- env var undefined/no opt-in = old behavior;
- env var defined/opted-in = new behavior.

The verification for Focal is OK on that regard (does not show the banner in step 5).

2) The autopkgtests for python2.7/focal failed, but this is not due to these changes.
I re-run the tests with the trigger migration-reference/0, and they continue to fail.

This is expected, since the changes are opt-in / are not enabled by default.
The only change which _is_ enabled by default is the new banner during build,
but that output is likely not checked for, I'd imagine (ie, it's OK to change).

3) There's been a recent rebuild of the autopkgtest database, and I'd have to
verify the status (ie, finished?) and impact (eg, report pages) at the moment
to make sure this is OK on that regard.