|
From: Lesley Binks on 5 May 2008 11:10 Hi I just did an 'apt-get upgrade -s' and found these updates were required Reading package lists... Done Building dependency tree... Done The following packages will be upgraded: cpio libperl5.8 linux-image-2.6.18-6-486 perl perl-base perl-doc perl-modules 7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Inst perl-modules [5.8.8-7etch2] (5.8.8-7etch3 Debian-Security:4.0/stable) Inst perl [5.8.8-7etch2] (5.8.8-7etch3 Debian-Security:4.0/stable) [] Inst libperl5.8 [5.8.8-7etch2] (5.8.8-7etch3 Debian-Security:4.0/stable) [] Inst perl-base [5.8.8-7etch2] (5.8.8-7etch3 Debian-Security:4.0/stable) Conf perl-base (5.8.8-7etch3 Debian-Security:4.0/stable) Inst linux-image-2.6.18-6-486 [2.6.18.dfsg.1-18etch1] (2.6.18.dfsg.1-18etch3 Debian-Security:4.0/stable) Inst cpio [2.6-18] (2.6-18.1+etch1 Debian-Security:4.0/stable) Inst perl-doc [5.8.8-7etch2] (5.8.8-7etch3 Debian-Security:4.0/stable) Conf perl (5.8.8-7etch3 Debian-Security:4.0/stable) Conf perl-modules (5.8.8-7etch3 Debian-Security:4.0/stable) Conf libperl5.8 (5.8.8-7etch3 Debian-Security:4.0/stable) Conf linux-image-2.6.18-6-486 (2.6.18.dfsg.1-18etch3 Debian-Security:4.0/stable) Conf cpio (2.6-18.1+etch1 Debian-Security:4.0/stable) Conf perl-doc (5.8.8-7etch3 Debian-Security:4.0/stable) So I did an 'apt-get upgrade' and got these problems Fetched 30.9MB in 9m37s (53.4kB/s) Preconfiguring packages ... (Reading database ... 157473 files and directories currently installed.) Preparing to replace perl-modules 5.8.8-7etch2 (using ..../perl-modules_5.8.8-7etch3_all.deb) ... Unpacking replacement perl-modules ... Preparing to replace perl 5.8.8-7etch2 (using ..../perl_5.8.8-7etch3_i386.deb) ... Unpacking replacement perl ... Preparing to replace libperl5.8 5.8.8-7etch2 (using ..../libperl5.8_5.8.8-7etch3_i386.deb) ... Unpacking replacement libperl5.8 ... Preparing to replace perl-base 5.8.8-7etch2 (using ..../perl-base_5.8.8-7etch3_i386.deb) ... Unpacking replacement perl-base ... Setting up perl-base (5.8.8-7etch3) ... (Reading database ... 157473 files and directories currently installed.) Preparing to replace linux-image-2.6.18-6-486 2.6.18.dfsg.1-18etch1 (using .../linux-image-2.6.18-6-486_2.6.18.dfsg.1-18etch3_i386.deb) .... The directory /lib/modules/2.6.18-6-486 still exists. Continuing as directed. Done. Unpacking replacement linux-image-2.6.18-6-486 ... Running postrm hook script /sbin/update-grub. You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub instead! Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /vmlinuz-2.6.18-6-486 Found kernel: /vmlinuz-2.6.18-5-486 Updating /boot/grub/menu.lst ... done Preparing to replace cpio 2.6-18 (using .../cpio_2.6-18.1+etch1_i386.deb) ... Unpacking replacement cpio ... Preparing to replace perl-doc 5.8.8-7etch2 (using ..../perl-doc_5.8.8-7etch3_all.deb) ... Leaving `diversion of /usr/bin/perldoc to /usr/bin/perldoc.stub by perl-doc' Unpacking replacement perl-doc ... Setting up libperl5.8 (5.8.8-7etch3) ... Setting up linux-image-2.6.18-6-486 (2.6.18.dfsg.1-18etch3) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-6-486/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-6-486/source Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Not updating initrd symbolic links since we are being updated/reinstalled (2.6.18.dfsg.1-18etch1 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.18.dfsg.1-18etch1 was configured last, according to dpkg) Running postinst hook script /sbin/update-grub. You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub instead! Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /vmlinuz-2.6.18-6-486 Found kernel: /vmlinuz-2.6.18-5-486 Updating /boot/grub/menu.lst ... done Setting up cpio (2.6-18.1+etch1) ... Errno architecture (i486-linux-gnu-thread-multi-2.6.22-3-amd64) does not match executable architecture (i486-linux-gnu-thread-multi-2.6.24.4) at /usr/local/share/perl/5.8.8/Errno.pm line 11. Compilation failed in require at /usr/sbin/install-info line 308. BEGIN failed--compilation aborted at /usr/sbin/install-info line 308. dpkg: error processing cpio (--configure): subprocess post-installation script returned error exit status 9 Setting up perl-modules (5.8.8-7etch3) ... Setting up perl (5.8.8-7etch3) ... Setting up perl-doc (5.8.8-7etch3) ... Errors were encountered while processing: cpio E: Sub-process /usr/bin/dpkg returned an error code (1) I don't have the time to fix this problem right now. I don't actually expect to have the time to repair this problem for about 12-14 days. So it seems like a good idea to post this problem and see if anyone else has experienced problems with this set of upgrades, if a bug has been raised, whether I face a complete re-install or not, or whether the whole situation is completely recoverable in some way. If anyone can shed some light on what I should do I will let you know how I got on in about two week's time. I'm running a Barton core btw. Thanks in advance Lesley -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Douglas A. Tutty on 5 May 2008 22:10 On Mon, May 05, 2008 at 04:01:42PM +0100, Lesley Binks wrote: > I just did an 'apt-get upgrade -s' and found these updates were required > Preparing to replace cpio 2.6-18 (using .../cpio_2.6-18.1+etch1_i386.deb) ... > Unpacking replacement cpio ... > Setting up cpio (2.6-18.1+etch1) ... > Errno architecture (i486-linux-gnu-thread-multi-2.6.22-3-amd64) does > not match executable architecture > (i486-linux-gnu-thread-multi-2.6.24.4) at > /usr/local/share/perl/5.8.8/Errno.pm line 11. > Compilation failed in require at /usr/sbin/install-info line 308. > BEGIN failed--compilation aborted at /usr/sbin/install-info line 308. > dpkg: error processing cpio (--configure): > subprocess post-installation script returned error exit status 9 > Errors were encountered while processing: > cpio > E: Sub-process /usr/bin/dpkg returned an error code (1) > > I don't have the time to fix this problem right now. I don't actually > expect to have the time to repair this problem for about 12-14 days. > > So it seems like a good idea to post this problem and see if anyone > else has experienced problems with this set of upgrades, if a bug has > been raised, whether I face a complete re-install or not, or whether > the whole situation is completely recoverable in some way. > > If anyone can shed some light on what I should do I will let you know > how I got on in about two week's time. > > I'm running a Barton core btw. I don't know what a Barton core is. I'm running i386 and amd64 on two different boxes (with an i386 chroot too) and didn't have a problem. Right now, you should have the new cpio unpacked and therefore the new binaries will be used. You could look at /var/lib/dpkg/info/cpio* The related scripts seem to be setting up update-alternatives. Try running the scripts manually and track the problem. Unfortunatly, since cpio is required, you can't just easily remove it and then install it. Doug. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
|
Pages: 1 Prev: Errors on upgrading from etch to lenny Next: Debian + LVM + RAID1 |