reassign 495394 libperl5.10 severity important thanks Peter Eisentraut [2008-08-17 12:02 +0300]: > > Actually, the solution is that postgresql-plperl-8.1 needs to be > > re-built for 5.10. > > That is not possible, because postgresql-plperl-8.1 is part of etch.
Indeed this is a tricky situation. -8.1 is *only* in etch, lenny has -8.3 (which of course uses Perl 5.10). The intended procedure is that the -8.1 packages stay around, the user installs -8.3, uses pg_upgradecluster for doing the upgrade (after the dist-upgrade to lenny), and if all is well, removes the psql 8.1 related packages (this is explained in debconf, README, manpages, etc.) So we can't rebuild -8.1 in etch against 5.10, and can't provide an -8.1 package in lenny against 5.10, since we can't support old versions forever. > What is in perl-base that libperl needs anyway? I actually wondered about the same. The entire idea of SONAMEs is that you can install multiple libfoo* in parallel. In this case you cannot install libperl5.8 and libperl5.10 in parallel, since they both have a strict versioned dependency on perl-base. As a shared library, ideally libperl5.x would only depend on the shared libs it links to, i. e. libc6. If the library really calls programs from perl-base, then maybe the dependency could at least be unversioned? This doesn't only break older postgresql versions, but any third-party or locally installed package which links against libperl5.8, thus raising the severity (I was inclined to set it to serious, but not without discussing it first). Thanks for any insight, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
