Your message dated Mon, 4 Aug 2008 20:34:46 +0200 (MEST)
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#492816: libperl must NOT be installed in /usr/lib
has caused the Debian Bug report #492816,
regarding libperl must NOT be installed in /usr/lib
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
492816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492816
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: perl
Version: 5.10.0-11
Severity: critical
Justification: breaks unrelated software
debian makes it impossible to install perls in other prefixes by forcing
libperl.so (a private library that should not be in the default search
path) into /usr/lib, where it clashes with every other libperl.
To be precise, the issue is that libperl is not abi-compatible with all
other libperl's on the same sytem.
Perl itself correctly manages this by not putting it's config-dependent
libraries in the default search path, but into an architetcure and
installation specific subdirectory in it's library dir.
Unfortunately, debian completely breaks this mechanism by moving it into
/usr/lib, where it clashes with all other libperls on the same system, as
/usr/lib is alwas in the default linker search path. i.e.
-L/opt/perl/lib/CORE -lperl
will link against the correct perl library (here in /opt/perl/lib) on
every system except on debian, as debian puts the libperl into the default
library search path, when libperl was never intended to be put there.
The fix is simply to not override perl's management mechanism that deals
corretcly with it and putting
the perl library into the corretc directory.
If libperl.so.5.* MUST reside in /usr/lib (debian policy says so) then
at the very least the linker libs (.a and .so) must be moved out of the
default library path.
As it is, it isn't possible to install another perl in the same system as
debian, and the reason is the (unneeded) breaking of the mechanism pwerl
uses to separate it's libraries by debian.
(this is especially bad as debian uses some extremely bad choices for
configuration, such as enabling the windows process emulation on unix,
which serves no purpose except slow down perl considerably for no gain
whatsoever on unix, so compiling one's own is practically required)
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages perl depends on:
hi libc6 2.7-12 GNU C Library: Shared libraries
ii libdb4.6 4.6.21-10 Berkeley v4.6 Database Libraries [
ii libgdbm3 1.8.3-3 GNU dbm database routines (runtime
ii perl-base 5.10.0-11 The Pathologically Eclectic Rubbis
ii perl-modules 5.10.0-11 Core Perl modules
Versions of packages perl recommends:
ii netbase 4.32 Basic TCP/IP networking system
ii perl-doc 5.10.0-10 Perl documentation
-- no debconf information
--- End Message ---
--- Begin Message ---
Now that Marc Lehmann demonstrated he does not understand Linux
it is time to close the bug.
Ahora también puedes acceder a tu correo Terra desde el móvil.
Infórmate pinchando aquí.
--- End Message ---
