On Fri, Aug 26, 2016 at 12:10:29AM +0200, gregor herrmann wrote: > On Sun, 21 Aug 2016 13:18:33 +0200, Marco d'Itri wrote: > > > YAML::XS adds an extra \n at the end of each line. > > The YAML module cannot read the generated files. > > Test case attached. > > This seems to be fixed in newer versions which we have in git. > > The problem is that we have a lintian ftp-master autoreject problem: > E: libyaml-libyaml-perl: embedded-library > usr/lib/perl5/auto/YAML/XS/LibYAML/LibYAML.so: libyaml > > I've already created a branch gregoa/use-system-yaml which uses the > system libyaml; no big deal, except that the tests fail because the > embedded libyaml in libyaml-libyaml-perl is patched :/ > > Some time ago I updated the patch so that the tests pass; which > always feels a bit cheap but according the the notes that past me > added to the patch headers, the changes are related to changes in the > embedded stuff and go back to original test code in the distribution.
Making it possible to use a system libyaml is discussed in https://github.com/ingydotnet/yaml-libyaml-pm/issues/49 and convincing upstream would be much better than doing so against their wish, particularly as this would create a functionality difference. The embedded libyaml is not a regression (see #664224) and not a release critical issue as far as I am aware. The lintian tag is overriddable. So I suggest we override the lintian error in order to fix this RC bug. -- Niko Tyni nt...@debian.org
