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

[Scott Moser]

It is a bug to change content in backwards incompatible ways.  livecd-
rootfs produced an artifact that is indexed with known-content.  A
change broke consumers of that content.  Thats a regression.

Pretending otherwise is wasting both of our time.

I pointed at one known consumer (owned by the same team that produces
the content) that will be affected by this backwards incompatible
change.  There are undoubtedly others.  Software *does* exist outside of
the Ubuntu archive, and even outside of launchpad.  Often times that
software builds on top of Ubuntu.  We generally consider that a *good*
thing.  It is not a good thing when Ubuntu breaks that other software
and gives a lame excuse.


I'll ask again... Why not just add a new file that has the content you want?
Then you don't break existing users *and* you have the content you want.

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

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

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