Re: ugh... erectile dysfunction
On Wed, Dec 06, 2000 at 10:56:48AM -0500, Aaron Solochek wrote:
> Both of those (perl-5.6 and perl-5.6-base are installed. By removing a large portion of my X system I reduced the
> errors to just those relavent to debconf:
>
> Setting up debconf (0.5.32) ...
> Data::Dumper object version 2.101 does not match $Data::Dumper::VERSION 2.09 at
you seem to be having a version problem in your Perl installation,
which probably has nothing to do with debconf. I suspect you will get
the same error when you simply try to run
perl -e "use Data::Dumper;"
which just loads the module in question (if everything goes fine,
this command should not output anything...)
If you do get a version mismatch message similar to the one above, I
would guess that you have an ancient version of the module Data::Dumper
somewhere on your system, which for some reason gets pulled in before
the one that comes with the recent version of Perl (Data::Dumper
version 2.101 has been out since April 1999)
A little background info: Every architecture dependent Perl module like
Data::Dumper consists if two parts:
the Perl-side module (.../Data/Dumper.pm) and the architecture-specific
shared object file (.../<arch>/auto/Data/Dumper.so) that gets pulled in via
the Dynaloader module. Both parts have to be exactly the same version, or
else you get the above message...
In your case, the "2.101" belongs to the .so-file, while the "2.09" comes
from the .pm-file, which indicates that the Perl-side .pm-file is the
wrong (older) version.
You might want to try running the following statement, which should tell
you, in which directory the file is being found:
perl -e 'for (@INC) { print "$_\n" if -f "$_/Data/Dumper.pm";}'
(If you have a look into the source of this Dumper.pm you should find
something like $VERSION = '2.09' at the very beginning...)
The search path where Perl looks for (.pm-)modules is determined by
the @INC-Array, which again may be manipulated by setting the environment
PERLLIB or PERL5LIB (among other things).
Maybe the place where Dumper.pm is found will give a clue as to what
is going wrong... (old version lying around somewhere, etc.?)
Other useful commands that might help to clarify things include
perl -V (for search paths etc.)
or setting the environment variable PERL_DL_DEBUG to 1, which should
trigger the Dynaloader to output a little on what it's doing...
(You might also try wether you get different results from running
"perl -V" versus "/usr/bin/perl -V", which would indicate that
you have several Perl versions (binaries) on your system/search path)
HTH,
Erdmut
> /usr/lib/perl5/5.6/i386-linux/DynaLoader.pm line 219.
> Compilation failed in require at /usr/lib/perl5/Debconf/ConfigDb.pm line 82.
> BEGIN failed--compilation aborted at /usr/lib/perl5/Debconf/ConfigDb.pm line 82.
> Compilation failed in require at /usr/share/debconf/frontend line 23.
> BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 23.
> dpkg: error processing debconf (--configure):
> subprocess post-installation script returned error exit status 2
> dpkg: dependency problems prevent configuration of bsdmainutils:
> bsdmainutils depends on debconf; however:
> Package debconf is not configured yet.
> Package debconf-tiny which provides debconf is not installed.
> dpkg: error processing bsdmainutils (--configure):
> dependency problems - leaving unconfigured
--
Erdmut Pfeifer
science+computing gmbh
-- Bugs come in through open windows. Keep Windows shut! --
Reply to: