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

Dimitri John Ledkov launchpad at surgut.co.uk
Tue Nov 13 17:39:13 UTC 2018


It's been extended in a backwards compatible manner.

Is this just an observation, or is something broken?

You correctly state what the format was, what the format has become, but
I don't see an actual bug report stated anywhere as to anything being
broken by this.

Because yes, the format of the manifest has changed. Intentionally.

Failing to find a bugreport in this bug....

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

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

-- 
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:
  New
Status in livecd-rootfs package in Ubuntu:
  New

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



More information about the foundations-bugs mailing list