The acks of the MIR process are given, but I was made aware why we can not see it in component mismatches, as we expected a seed change there.
Thanks to Miriam we've sorted out that the seed change only landed in Plucky (because that was the devel release at the time). But since this was in-flight it didn't make it into questing on the archive opening. So we realized in checking that it is trying to move ONLY in plucky [1], but that isn't the way to start. As usual please, add it to -devel first to avoid this to regress functionality on upgrades. Please do the same seed change to questing, when it is shown is mismatches then let us promote it there. You can yourself or with your partners have a look if it works as intended in the -devel release. Then next, we can act on the plucky promotion based on [1] as well. Let me add bug tasks to represent that, if later on more release follow we might need to check if the conditions there are different - but that is then. [1]: https://ubuntu-archive-team.ubuntu.com/germinate- output/ubuntu.plucky/all ** Also affects: azure-vm-utils (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: azure-vm-utils (Ubuntu Questing) Importance: Undecided Status: In Progress ** Changed in: azure-vm-utils (Ubuntu Plucky) Status: New => In Progress ** Changed in: azure-vm-utils (Ubuntu Questing) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2093322 Title: [MIR] azure-vm-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/azure-vm-utils/+bug/2093322/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
