Your message dated Fri, 12 Jan 2018 13:56:14 +0100
with message-id <aecb2d09-912e-c1b1-aebf-9d5dfb334...@debian.org>
and subject line Re: Bug#883933: nmu: polymake_3.1-5
has caused the Debian Bug report #883933,
regarding nmu: polymake_3.1-5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
883933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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"

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message ---
On 06/01/18 20:15, Niko Tyni wrote:
> 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.

Agreed. This needs to be properly fixed, whether in perl to look for the modules
in other micro version directories, or in polymake to have stricter dependencies
on perl. Since the former is being addressed in #886494, I'm closing this.

Cheers,
Emilio

--- End Message ---

Reply via email to