Comment 2 for bug 1626070

We knew it would happen for migrations, but you are right it is critical if people just start old (wrong) defines.
We certainly fixed the right issue, but yes the (correct) removal of the wily type which was the (wrong) default of xenial before can break new starts of former machines.

Damn - yes we have to add the type again ASAP - but not as default.
To avoid too much fallout.

Thanks for the report, we did so much testing on migrations and pre/post upgrade things that we seemed to miss the obvious one.

I'll create a debdiff asap and upload.
That wily type will be identical to the one we had (which also is the same as the new ubuntu.xenial type which is why the reported fix worked)