Comment 2 for bug 1727693

The best protection for this would be an autopkgtest that would block landing of distro-info-data. It's clear the existing tests didn't stop this, although as mentioned, there is are future-provider tests that play with this idea. Ensuring juju works and responds as expected would best be done in a unit test imho, which have been expanded in light of the changes made. I believe the only remaining question for me is ensuring juju will always bootstrap to something (by adding a hardcoded backup default), as well as what the default bootstrap option will be.