Bug#865720: libconfig-model-dpkg-perl: hard-codes the list of virtual packages, mistake in recent update

On Sat, 24 Jun 2017 19:13:28 +0200 Dominique Dumont wrote: > In the meantime, I'll fix the mistake I made with the list of virtual packages. This mistake is fixed in libconfig-model-dpkg-perl 2.096 (released on 2017-06-24) I'll leave this bug open to track the requirement to

Bug#865720: libconfig-model-dpkg-perl: hard-codes the list of virtual packages, mistake in recent update

On Sat, 2017-06-24 at 19:24 +0200, Dominique Dumont wrote: > I find YAML easier to write by hand. I would strongly suggest never using YAML if you can avoid it. The parsers in multiple languages (at least Perl, Python) default to unsafe loading that allows loading arbitrary code in some

Bug#865720: libconfig-model-dpkg-perl: hard-codes the list of virtual packages, mistake in recent update

On Saturday, 24 June 2017 09:39:54 CEST Russ Allbery wrote: > These days, I normally use JSON for that sort of thing. Does that seem > reasonable, or is there a reason to use some other format instead? At the risk of showing my Perl background, I tend to dislike JSON because of the syntax

Bug#865720: libconfig-model-dpkg-perl: hard-codes the list of virtual packages, mistake in recent update

On Friday, 23 June 2017 23:39:36 CEST Russ Allbery wrote: > It's worth noting that registering a virtual package with Policy is > optional if it is used among a cooperating set of packages, and there are > numerous virtual packages in Debian that are not listed there. Indeed,

Bug#865720: libconfig-model-dpkg-perl: hard-codes the list of virtual packages, mistake in recent update

Paul Wise writes: > On Fri, 2017-06-23 at 23:39 -0700, Russ Allbery wrote: >> That said, if there's some desire for automated consumption of the list >> from the Policy package, I'd be happy to provide it in a >> machine-readable format.  I wonder if there would be some merit in

Bug#865720: libconfig-model-dpkg-perl: hard-codes the list of virtual packages, mistake in recent update

On Fri, 2017-06-23 at 23:39 -0700, Russ Allbery wrote: > It's worth noting that registering a virtual package with Policy is > optional if it is used among a cooperating set of packages, and there are > numerous virtual packages in Debian that are not listed there. I think that the list is only

Bug#865720: libconfig-model-dpkg-perl: hard-codes the list of virtual packages, mistake in recent update

Paul Wise writes: > libconfig-model-dpkg-perl hard-codes the list of virtual package names > in the @virtual_list array in the lib/Config/Model/Dpkg/Dependency.pm > file. The authoritative list is available in the debian-policy package. > Config::Model::Dpkg should depend on

Bug#865720: libconfig-model-dpkg-perl: hard-codes the list of virtual packages, mistake in recent update

Package: libconfig-model-dpkg-perl Version: 2.090 Severity: wishlist Usertags: hardcoding libconfig-model-dpkg-perl hard-codes the list of virtual package names in the @virtual_list array in the lib/Config/Model/Dpkg/Dependency.pm file. The authoritative list is available in the debian-policy