severity 808629 serious block 808629 with 798096 block 796345 by 808629 affects 808629 usrmerge affects 798096 usrmerge thanks
On Mon, Dec 21, 2015 at 06:16:10PM +0200, Niko Tyni wrote: > On Mon, Dec 21, 2015 at 05:06:36PM +0100, Marco d'Itri wrote: > > On Dec 21, Niko Tyni <nt...@debian.org> wrote: > > > > > Thanks. I suspect the critical severity is a pun (as in "breaks the > > > whole system() [call]"), but in case it isn't, please provide some > > > justification. Downgrading for now. > > It breaks unrelated software, so I think that it fits... > > A script using the autodie module is not unrelated software. However, as this perl regression completely breaks usrmerge (whose postinst now fails at installation time), I guess some part of this should be release critical. I'm marking the clone against the perl package that for now, although I'm sure usrmerge could be changed to work around this if it turns out to be necessary. So transitioning Perl 5.22 from unstable to testing would break usrmerge in testing, which means this is an issue for the whole transition. Once there's a fix, the separate libautodie-perl needs to be fixed first so that installing it over the Perl core version will not reintroduce the bug. FWIW I made some progress on the upstream ticket yesterday but it's not quite there yet. It would have been nice to hear about this earlier. -- Niko Tyni nt...@debian.org
