On Thu, Apr 30, 2020 at 07:16:01PM -0000, Ryan Harper wrote:
> cloud-init invokes growpart
> growpart is from cloud-guest-utils
> cloud-init depends on cloud-guest-utils
> cloud-guest-utils depends on util-linux
>
> So, when fdisk was split out, we now miss a dependency.
>
> How, in generate does one protect against packaging changes which remove
> dependent parts?
(Given that this package change happened early last cycle, I don't know
how feasible tracking down if they didn't run/were ignored would be;
perhaps a more distro-focused person could help?)
On Thu, Apr 30, 2020 at 07:16:01PM -0000, Ryan Harper wrote:
> cloud-init invokes growpart
> growpart is from cloud-guest-utils
> cloud-init depends on cloud-guest-utils
> cloud-guest-utils depends on util-linux
>
> So, when fdisk was split out, we now miss a dependency.
>
> How, in generate does one protect against packaging changes which remove
> dependent parts?
I was going to say that I expect we would have caught this if /git.launchpad. net/ubuntu/ +source/ cloud-utils/ tree/debian/ tests
cloud-guest-utils had autopkgtests that exercised the sfdisk dependency,
but it appears we already do have such autopkgtests:
https:/
(Given that this package change happened early last cycle, I don't know
how feasible tracking down if they didn't run/were ignored would be;
perhaps a more distro-focused person could help?)