On Thu, Apr 30, 2020 at 2:50 PM Steve Langasek <[email protected]> wrote:
> On Thu, Apr 30, 2020 at 05:27:49PM -0000, Dimitri John Ledkov wrote: > > Looking at seeds, it seems like maybe "cloud-image" should have fdisk > > seeded in both focal & groovy. > > I think this belongs in the server seed, not just cloud-image. >From the changelog you dropped fdisk to avoid having it in chroots and squashfs'. Adding it to the seed would negate that without then removing it again from those images, which feels fragile. I read the removal of fdisk as direction for the OS generally and will note the chroots and squashfs still carry gdisk/sgdisk (Although now I can't figure out how that gets into the image). But why wouldn't we leave it out of the seeds and if the user needs fdisk in addition to gdisk then they must now explicitly install it? > But given that fdisk is no longer part of the essential set, packages that > invoke it should also be fixed to declare a dependency on it. > +1 on packages explicitly declaring a dependency. Is this being worked for cloud-utils? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876139 Title: Groovy cloud-images failing during growpart To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1876139/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
