On Fri, 22 May 2009, Marc Haber wrote: > with dpkg 1.15.1 installed, installation of perl 5.10.0-22 fails due > to an error message in update-alternatives: > $ sudo dpkg --install /var/cache/apt/archives/perl_5.10.0-22_i386.deb > (Reading database ... 16660 files and directories currently installed.) > Preparing to replace perl 5.10.0-22 (using .../perl_5.10.0-22_i386.deb) ... > Unpacking replacement perl ... > Setting up perl (5.10.0-22) ... > update-alternatives: warning: forcing reinstallation of alternative > /usr/bin/rename-5.005 because link group rename is broken. > Can't call method "slave" on an undefined value at > /usr/sbin/update-alternatives line 1011. > dpkg: error processing perl (--install): > subprocess installed post-installation script returned error exit status 2 > Processing triggers for man-db ... > Errors were encountered while processing: > perl > > The "Can't call method on an undefined value" looks like this is not > perl's fault.
Can you provide me /var/lib/dpkg/alternatives/rename ? It looks like some left over alternatives in that file dating back to the perl 5.005 transition that was not properly cleaned... I certainly upgraded perl to version 5.10.0-22 on my system without encountering any error. There is likely a lack of checks in update-alternatives but also something not 100% clean in the perl upgrade history. The new code tries harder to avoid problems and your installation is somehow broken (and it failed while trying to fix it). And please show me the output of this command: ls -al /etc/alternatives/rename /usr/bin/rename-5.005 /usr/bin/rename In fact, looking at the code more closely, the problem is probably that /etc/alternatives/rename points to an non-existing and unregistered alternative... (i.e. it doesn't appear in /var/lib/dpkg/alternatives/rename). Let's see if I'm right. Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
