Bug#353761: perl: Perl lib version (v5.8.4) doesn't match executable

2006-02-20 Thread Ulrich Fürst
Package: perl
Version: 5.8.7-10
Severity: grave
Justification: renders package unusable

I upgraded my computer from debian sarge to etch a while ago and
can't get rid of the following message:
# apt-get -f install
--- snip ---
Setting up libpango1.0-common (1.10.3-1) ...
Updating the modules list for Pango-1.4.0...done.
Perl lib version (v5.8.4) doesn't match executable version (v5.8.7) at\
 /usr/lib/perl/5.8/Config.pm line 32.
Compilation failed in require at /usr/share/perl/5.8/File/Copy.pm line 15.
BEGIN failed--compilation aborted at /usr/share/perl/5.8/File/Copy.pm line 15.
Compilation failed in require at /usr/bin/defoma-app line 7.
BEGIN failed--compilation aborted at /usr/bin/defoma-app line 7.
Failed to clean up for defoma: 65280 at /usr/sbin/update-pangox-aliases line 49.
dpkg: error processing libpango1.0-common (--configure):
 subprocess post-installation script returned error exit status 255
Setting up xfonts-scalable (6.9.0.dfsg.1-4) ...
Perl lib version (v5.8.4) doesn't match executable version (v5.8.7) at\
 /usr/lib/perl/5.8/Config.pm line 32.
Compilation failed in require at /usr/share/perl/5.8/File/Copy.pm line 15.
BEGIN failed--compilation aborted at /usr/share/perl/5.8/File/Copy.pm line 15.
Compilation failed in require at /usr/bin/defoma-app line 7.
BEGIN failed--compilation aborted at /usr/bin/defoma-app line 7.
dpkg: error processing xfonts-scalable (--configure):
 subprocess post-installation script returned error exit status 255
Errors were encountered while processing:
 libpango1.0-common
--- snip ---

This happens with several packages (e.g. xfonts-scalable), so these
packages aren't installable. They stay unconfigured.

$ perl -V
Perl lib version (v5.8.4) doesn't match executable version (v5.8.7)\
 at /usr/lib/perl/5.8/Config.pm line 32.
Compilation failed in require.
BEGIN failed--compilation aborted.

I tried to reinstall all perl packages with:
# dpkg --force-overwrite -i perl_5.8.7-10_i386.deb perl-base_5.8.7-10_i386.deb \
  perl-modules_5.8.7-10_all.deb libperl5.8_5.8.7-10_i386.deb

didn't lead to anything. The same with perl purged (with --forec) 
before reinstallation.

It happens with other parts of perl to. This is a mail from cron:
/etc/cron.daily/apt-show-versions:
Perl lib version (v5.8.4) doesn't match executable version (v5.8.7) at 
/usr/lib/perl/5.8/Config.pm line 32.
Compilation failed in require at /usr/lib/perl/5.8/DynaLoader.pm line 24.
BEGIN failed--compilation aborted at /usr/lib/perl/5.8/DynaLoader.pm line 24.
Compilation failed in require at /usr/lib/perl/5.8/Storable.pm line 8.
Compilation failed in require at /usr/bin/apt-show-versions line 35.
BEGIN failed--compilation aborted at /usr/bin/apt-show-versions line 35.
run-parts: /etc/cron.daily/apt-show-versions exited with return code 255


Ulrich Fürst


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (700, 'testing')
Architecture: i386 (i586)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2-386
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages perl depends on:
ii  libc6 2.3.5-13   GNU C Library: Shared libraries an
ii  libdb4.3  4.3.29-4   Berkeley v4.3 Database Libraries [
ii  libgdbm3  1.8.3-2GNU dbm database routines (runtime
ii  perl-base 5.8.7-10   The Pathologically Eclectic Rubbis
ii  perl-modules  5.8.7-10   Core Perl modules
ii  libperl5.85.8.7-10   Shared Perl library


Versions of packages perl recommends:
pn  perl-doc   (no description available)

-- no debconf information



Bug#353761: perl: Perl lib version (v5.8.4) doesn't match executable

2006-02-21 Thread Ulrich Fürst
Steve Langasek <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 20, 2006 at 07:43:59PM +0100, Ulrich Fuerst wrote:
> > Package: perl
> > Version: 5.8.7-10
> > Severity: grave
> > Justification: renders package unusable
> 
> > I upgraded my computer from debian sarge to etch a while ago and
> > can't get rid of the following message:
> > # apt-get -f install
> > --- snip ---
> > Setting up libpango1.0-common (1.10.3-1) ...
> > Updating the modules list for Pango-1.4.0...done.
> > Perl lib version (v5.8.4) doesn't match executable version (v5.8.7)
> > at\ /usr/lib/perl/5.8/Config.pm line 32.
> > Compilation failed in require at /usr/share/perl/5.8/File/Copy.pm
> > line 15. BEGIN failed--compilation aborted at /usr/share/perl/5.8/
> > File/Copy.pm line 15. Compilation failed in require at /usr/bin/
> > defoma-app line 7. BEGIN failed--compilation aborted at /usr/bin/
> > defoma-app line 7.
> 
> Please forward the output of ls -ld /usr/lib/perl/5.8 to this bug.

ls -ld /usr/lib/perl/5.8
drwxr-xr-x  27 root root 4096 2006-02-20 15:02 /usr/lib/perl/5.8/


> This should be a symlink belonging to the perl-base package, and it
> should be pointing at /usr/lib/perl/5.8.7.  Yours apparently is not.
> I suspect this is an instance of local breakage, not a packaging bug.

Shouldn't this have been fixed with dpkg --force-overwrite? At least
with purging the package and reinstalling it?

I made a symlink now:
ls -ld /usr/lib/perl/5.8
lrwxrwxrwx  1 root root 5 2006-02-21 10:46 /usr/lib/perl/5.8 -> 5.8.7/
and that fixed the problem. 

Ulrich


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#353761: perl: Perl lib version (v5.8.4) doesn't match executable

2006-02-21 Thread Ulrich Fürst
Brendan O'Dea <[EMAIL PROTECTED]> wrote:
> 
> It is possible that the cause of this problem is a package which has
> mistakenly installed to the CORE (archlib=/usr/lib/perl/5.8) rather
> than vendor directories.
> 
> If such a package were to be installed *before* perl, then a directory
> would be created, which dpkg would then honour when unpacking perl,
> rather than creating the symlink.

Then this had to be an essential package, doesn't it? So I guess this
would have been detected long ago.
 
> Please check the output of 'dpkg -S /usr/lib/perl/5.8'.  You should
> only get 'perl-base' as a match.  If any other packages appear,
> please file a bug on that package.

That's o.k. here. So this is infact a local issue, even if I
don't know how it happend. But that's my own problem, not yours!

Thank you for the help!

Ulrich Fürst