IIRC the packaging is tried to be consistent and the same across releases. Currently it has "netplan.io | ifupdown"
Surely it could be dropped to be only "netplan.io" but that will make backports (slightly) more effort. This was pulling in ifupdown in the past and no more did so for a while. Recently the package src:ifupdown2 added a provides: ifupdown That made it show up again on component mismatches. I'd have expected that component mismatches would consider things to be "ok if there is a sufficient dependency in main". Instead of "flag it as mismatch if there is any package having a provides". I talked with doko in the MIR meeting and he first suggested Extra- Excludes but then wanted to discuss that with Colin first to then get back to us. Options mentioned so far: 1. cloud-init to drop ifupdown dependency and adding it back on backports 2. Add Extra-Excludes to seeds to mask this from being added 3. fix tooling that generates component mismatches to consider "Provides" in a different way @Doko if you could reply on this bug once you have talked with Colin that would be great -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855557 Title: please drop ifupdown depedency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1855557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
