I don't see any protocol problems in the log.
May 19 10:13:11 in-target: debconf (developer): ----> DATA debconf-apt-progress/info type text
May 19 10:13:11 in-target: debconf (developer): <---- 0 OK
May 19 10:13:11 in-target: Use of uninitialized value $x in scalar assignment at /usr/share/perl/5.10/utf8_heavy.pl line 242, <GEN0> line 1.
May 19 10:13:11 in-target: Use of uninitialized value $x in pattern match (m//) at /usr/share/perl/5.10/utf8_heavy.pl line 243, <GEN0> line 1.
May 19 10:13:11 in-target: Use of uninitialized value in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68, <GEN0> line 1.
May 19 10:13:11 in-target: Use of uninitialized value in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68, <GEN0> line 1.
May 19 10:13:11 in-target: debconf (developer): ----> DATA debconf-apt-progress/info description Preparing eject
debug developer => "<---- $reply";
my ($tag, $val) = split(' ', $reply, 2);
The first line of code succeeded and printed $reply, which was the "0 OK".
In the second line of code, $reply has somehow become undef.
I don't understand how that could happen!
Apparently, perl's utf-8 output layer is coming into the picture -- that's
where the utf8_heavy comes into play. Perhaps it is somehow unsetting $reply.
--
see shy jo
Attachment:
signature.asc
Description: Digital signature