On Fri, Oct 31, 2008 at 11:13:25AM +0100, Sven Joachim wrote: > On 2008-10-31 03:24 +0100, Victor Munoz wrote: > > > Hello. I've got a very complex situation here with perl. I'm running > > sid, and last weekend's update left my system partially broken. > > It seems you had not upgraded for a long time (half a year at least). >
Not really, but I had been upgrading specific packages or groups of packages for several weeks/months. This was my first attempt at a full, blind upgrade in months. > This is a well known and hard to solve problem of the perl 5.8 -> 5.10 > upgrade. See the following bugs, for example: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482140 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503712 > Thanks for the reference. Problems were similar indeed. > > The reason is that the new perl-modules was unpacked first, and before > perl-base could be unpacked _another_ package was unpacked which had a > command in its preinst or prerm script that required a perl module from > the perl-modules package. Since the /usr/bin/perl command can no longer > find them (see the above "Can't locate File/Copy.pm..." error message), > that script fails and apt aborts the whole operation, leaving the system > in a bad state. > Yes, I guessed so. System was pretty messed up > > You need to get the perl packages in sync first. Since apt will not > help you (it insists of fixing broken packages first, and that cannot be > done), you have to invoke dpkg directly: > > # dpkg --unpack /var/cache/apt/archives/*perl*5.10.0-16* > > should do the trick¹, and aptitude will hopefully be able to fix the rest > automatically afterwards. > I have managed to do that eventually as I wrote in detail in another post of this thread, so now my system is not *so* broken. At least perl is ok, I think. Thanks for the help. Victor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
