[Bug 1803162] Re: non-dpkg information and broken format in manifest

[Dimitri John Ledkov]

No, that's not how it works. Lots of people are free to do whatever they
want and consume whatever they want. Consumers, are only those that we
care about. I have now been pointed to at least 4 forks of mfdiff, and
well, maxsplit=1 should be enough to fix the linesplits there.

The production code that does use manifests is known to not be broken.

Please stay on topic and please help identify things that are broken
with the new manifest, and used in production, if any.

The manifest format change to include snaps will not be reverted, based
on current information.

Do you have anything else to share that you are aware of to be broken?
either private or public?

(in addition to the already mentioned mfdiff, including all the public,
and private copies and forks of thereof)

** Changed in: cloud-images
       Status: New => Invalid

** Changed in: livecd-rootfs (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1803162

Title:
  non-dpkg information and broken format in manifest

Status in cloud-images:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Invalid

Bug description:
  Ubuntu images have been accompanied by a 'manifest' file since at least 10.04.
  This manifest file was a list of the dpkg installed packages and their versions.
  The format was as output by dpkg-query --show.
  That format was
    package-name<tab>version

  The offending change was added at
  https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/revision/1706

  The disco images now contain non-dpkg information in them.
  There are a few problems with this:
   a.) the format is now changed.  Some lines will now have 3 fields rather than 2.
   b.) content is not strictly a list of dpkg information.

  I understand the desire to have pre-seeded snap information in this file
  but believe that the correct way to add representation of that information
  is with new files rather extending in non-backwards compatible ways an
  existing file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1803162/+subscriptions