On Sat, Dec 09, 2017 at 11:32:12AM -0400, David Bremner wrote: > Package: release.debian.org > Severity: normal > User: release.debian....@packages.debian.org > Usertags: binnmu > > The following crash seems cured by a rebuild: > > Can't locate loadable object for module Polymake::Ext in @INC (@INC contains: > /usr/share/polymake/perllib /usr/lib/polymake/perlx/5.26.0 > /usr/lib/polymake/perlx /home/bremner/.config/perl /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 > /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 > /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at > /usr/share/polymake/perllib/Polymake/Namespaces.pm line 17. > > nmu polymake_3.1-5 . ANY . unstable . -m "rebuild for perl 5.26"
FWIW I don't think this is the correct way to fix this because it doesn't take partial upgrades into account at all. I've filed #886494 with some suggestions on better fixes. OTOH a binNMU doesn't hurt of course... -- Niko Tyni nt...@debian.org
