Comment 2 for bug 1779939

It seems to be the structure of snapcraft.yaml in subiquity that triggers it (though it might be a snapcraft bug). My suspicion is that the subiquity part has an implicit dependency on something (or an initialization step) provided by one of the other parts. This is my first exposure to snapcraft, so I'm afraid I'm not much use.