LinuxQuestions.org - [SOLVED] Suspected Perl issue on my Debian Sid install (maybe debconf related)

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Suspected Perl issue on my Debian Sid install (maybe debconf related) (https://www.linuxquestions.org/questions/debian-26/suspected-perl-issue-on-my-debian-sid-install-maybe-debconf-related-4175611326/)

Suspected Perl issue on my Debian Sid install (maybe debconf related)

So when I try to run a couple of commands

Code:

apt-file update

cpanm

cpan -u

My perl version

Code:

# perl -v



This is perl 5, version 26, subversion 0 (v5.26.0) built for x86_64-linux-gnu-thread-multi

(with 51 registered patches, see perl -V for more detail)

I get the following error

Code:

# cpan -u

ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)

#

ListUtil.c doesn't seem to exist

Code:

# locate ListUtil.c

#

from the searching I have done, it seems cpan (or cpanm) is the favoured route to update the libraries. But of course this problem seems to be preventing me from running them.

Now I don't know if this is related, but I noticed all this when an update failed with a debconf error

Code:

# dpkg -i /var/cache/apt/archives/debconf_1.5.63_all.deb

(Reading database ... 290546 files and directories currently installed.)

Preparing to unpack .../debconf_1.5.63_all.deb ...

Unpacking debconf (1.5.63) over (1.5.63) ...

Setting up debconf (1.5.63) ...

ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)

dpkg: error processing package debconf (--install):

 subprocess installed post-installation script returned error exit status 1

Errors were encountered while processing:

 debconf

Code:

# dpkg-reconfigure debconf

ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)

Now this may have been my fault by installing it anyway even with a bug listed

Code:

# apt-listbugs list debconf

Retrieving bug reports... Done

Parsing Found/Fixed information... Done

grave bugs of debconf (→ ) <Outstanding>

 b1 - #709198 - debconf: should not use python in maintainer scripts

Summary:

 debconf(1 bug)

But another 2 sid installs I have are running the same version of debconf and they are fine so I am not sure if this is a red herring.

Any thoughts would be appreciated

edit - the one difference the install with an issue has is that I tried to install a musicbrainz server on it

When you upgrade PERL via cpan you have to rebuild the modules that are not completely PERL code.

Quote:

Originally Posted by AwesomeMachine (Post 5745150)

When you upgrade PERL via cpan you have to rebuild the modules that are not completely PERL code.

that's the problem. perl is updated via apt (from stable 5.24 to 5.26).

so for instance, the issue in the op I resolved by removing List::Utils

Code:

cpanm --uninstall List::Util

while I had downgraded back down to the perl version in stable version (I actually installed via dpkg - perl, perl-base and libperl5.24)

So when I upgraded again to 5.26, the ListUtil error was gone and replaced by

Code:

# cpanm 

vxs.c: loadable library and perl binaries are mismatched (got handshake key 0xdb80080, needed 0xde00080)

I have not been able to determine which library this relates to

so yes trying to install musicbrainz server was what was causing issues as this installed perl modules via cpanm

lessons learnt:
- i might be a user of 10+ years on sid, but that doesn't mean i should not be prepared for things going north
- given the above it's especially important to remember that most guides will be done with the view of a stable install
- i have to be very careful with perl especially as it introduces packages outside of apt

1. so because i am on sid, perl had upgraded from 5.24 to 5.26
2. downgraded to 5.24 (the version in stable) using dpkg
3. cpanm was then able to work and I removed List::Util - cpanm --uninstall List::Util
4. upgraded perl back to the sid version
5. had to repeat steps 2 to 4 a number of times as new perl modules showed up that were impacted
6. eventually got the system to a point where the debconf install completed and I could do a full system upgrade