Comment 7 for bug 2073461

Updated the description to mention that python-argcomplete must be accepted into -proposed before virt-install. The SRU for the former does not need to block the SRU of the latter.

Relevant IRC discussion:

[12:02] <ogayot> ubuntu-sru: I would like to get virt-manager (bug 2073461) SRU-ed to noble ; but the package currently FTBFS because one of its build dependencies regressed (bug 2075315). Assuming the SRUs are approved, should I wait until the fixed build dependency makes it to noble-updates before seeking sponsoring for virt-install; or can both packages live in noble-proposed and migrate together?
[12:02] -ubottu:#ubuntu-release- Bug 2073461 in virt-manager (Ubuntu Noble) "[SRU] virt-install ignores --cloud-init when --location is present" [Undecided, New] https://launchpad.net/bugs/2073461
[12:02] -ubottu:#ubuntu-release- Bug 2075315 in python-argcomplete (Ubuntu Noble) "[SRU] argcomplete 3.1.4-1 is incompatible with default python version (3.12.3)" [Undecided, Confirmed] https://launchpad.net/bugs/2075315
[12:05] <ogayot> (I assume builders have -proposed enabled in stable series, too?)
[12:26] <rbasak> ogayot: no need to block one SRU on the other, based on your explanation above. However, we do need to accept into proposed in the correct order (or deal with rebuild attempts etc). Please explain that in the SRU documentation in the bug.
[12:32] <ogayot> rbasak: Thanks, I will document what's needed!

https://irclogs.ubuntu.com/2024/08/08/%23ubuntu-release.html