@Steve,
"We have never represented the .manifest to be a public machine-parseable
interface."
Thats clearly not true. Machine-formatted content (the .manifest)
advertised in a machine-formatted index (streams) is quite reasonable to
be expected to be machine parseable.
One example of something that parses that information is 'mfdiff'. I do
not know for sure, but I suspect it was broken. Anyone wanting to
determine if a specific/fixed version of a package would have come to
the decision to parse this file.
@Dimitri,
Changing the number of fields in a record of a tab delimited file and
*additionally* changing the meaning of an existing field is not backwards
compatible.
@Both,
Why not do this right? Add a .manifest.json file. You can determine the
format of the file.
** Changed in: cloud-images
Status: Incomplete => New
** Changed in: livecd-rootfs (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803162
Title:
non-dpkg information and broken format in manifest
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1803162/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
