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

[Scott Moser]

> No, that's not how it works.

I'm not sure I know what you were referring to.

Can you give a single justification for breaking existing consumers of a
deliverable?

I do not see justification anywhere.  Not in the commit message [1], the
merge proposal [2] or any of the comments here.  This is the sort of
thing I'd hope to see discussion of in a merge proposal.

I've pointed out that a change made is backwards incompatible.  I've
suggested ways you support including information about snap packages
(manifest.json).  I consider this on topic.

Is this change intended to be SRU'd ?  As a cosmic-forward change this
could be acceptable, but even then... Why?

[1] https://code.launchpad.net/~codyshepherd/livecd-rootfs/snaps-manifest/+merge/358530
[2] https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/revision/1714

-- 
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