Author: Joey HessJoey Hess
Date: May 20, 2008 16:50
I've reproduced this and done some debugging.
If I install perl (not just perl-base), the uninitialised value goes away!
I'm leaning solidly toward this being a perl problem now, and it seems
it's a problem in the perl-base package, possibly missing something pulled
in if full perl is installed.
It seems that the call to split is sometimes causing this uninitalised value
warning. I've verified that it can happen when $reply has a value such as "0
multiselect escape " when going into the split. And it is still defined when
coming out, AND both values split out are defined and correct. So what's
uninitialised?
Here's a backtrace I got of how SWASHNEW gets called. This call seems
to be done implicity by perl.
May 20 23:05:11 in-target: utf8::SWASHNEW('utf8', 'IsSpacePerl', undef, 1, 0) called at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 74
May 20 23:05:11 in-target: Debconf::FrontEnd::Passthrough...
|