Bug#627566: marked as done (rough transition to 486)
Your message dated Mon, 17 Feb 2014 15:20:11 +0000
with message-id <E1WFPzP-0005qk-3v@franck.debian.org>
and subject line Bug#627566: fixed in ldc 0.13.0alpha1-1
has caused the Debian Bug report #627566,
regarding rough transition to 486
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 owner@bugs.debian.org
immediately.)
--
627566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627566
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-686
If we are going to end up with -486, things could be smoother.
First it would be great if we didn't need to download the big .deb only
to find out we can't use it... OK, never mind that.
Upon aptitude upgrade
We see this six (6) times
│ This system requires a different kernel configuration │
│ │
│ Debian's '686' kernel configuration has been replaced by the '686-pae' configuration, which uses PAE │
│ (Physical Address Extension). However, the CPU in this system does not support PAE. │
│ │
│ You should install linux-image-486 and remove linux-image-686 and/or linux-image-2.6-686 if they are │
│ currently installed.
And the grub etc. stuff gets run anyway:
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.39-1-686-pae /boot/vmlinuz-2.6.39-1-686-pae
update-initramfs: Generating /boot/initrd.img-2.6.39-1-686-pae
run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.39-1-686-pae /boot/vmlinuz-2.6.39-1-686-pae
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 2.6.39-1-686-pae /boot/vmlinuz-2.6.39-1-686-pae
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.39-1-686-pae
Found initrd image: /boot/initrd.img-2.6.39-1-686-pae
Found linux image: /boot/vmlinuz-2.6.38-2-686
Found initrd image: /boot/initrd.img-2.6.38-2-686
Found linux image: /boot/vmlinuz-2.6.38-1-686
Found initrd image: /boot/initrd.img-2.6.38-1-686
done
Setting up libapr1 (1.4.5-1) ...
Setting up libfuse2 (2.8.4-1.5) ...
Setting up linux-image-686-pae (2.6.39+35) ...
Setting up linux-image-2.6-686 (2.6.39+35) ...
dpkg: error processing linux-image-2.6-686 (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up linux-image-686 (2.6.39+35) ...
configured to not write apport reports
dpkg: error processing linux-image-686 (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up linux-libc-dev (2.6.39-1) ...
configured to not write apport reports
Setting up libdc1394-22 (2.1.3-4) ...
Setting up perl-modules (5.12.3-7) ...
Setting up perl (5.12.3-7) ...
Setting up rpm (4.9.0-5) ...
Setting up libnetaddr-ip-perl (4.044+dfsg-1) ...
Setting up perl-doc (5.12.3-7) ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.39-1-686-pae
Errors were encountered while processing:
linux-image-2.6-686
linux-image-686
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up linux-image-686 (2.6.39+35) ...
dpkg: error processing linux-image-686 (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up linux-image-2.6-686 (2.6.39+35) ...
dpkg: error processing linux-image-2.6-686 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-686
linux-image-2.6-686
Now we attempt to do as told. Of course we dare not remove the running kernel.
# aptitude install linux-image-486
The following NEW packages will be installed:
linux-image-2.6.39-1-486{a} (D: linux-image-486, S: firmware-ipw2x00, S: firmware-linux-free, S: firmware-linux-nonfree, S: firmware-realtek) (for linux-image-486)
linux-image-486
The following partially installed packages will be configured:
linux-image-2.6-686 linux-image-686
0 packages upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 28.5 MB of archives. After unpacking 82.6 MB will be used.
Do you want to continue? [Y/n/?]
Here we get four more of the above banner.
We also find we must purge linux-image-686 linux-image-2.6-686 linux-image-2.6.39-1-686-pae linux-image-686-pae
I.e., four packages, not just one or two as mentioned in the banner.
We now get
The link /vmlinuz.old is a damaged link
Removing symbolic link vmlinuz.old
You may need to re-run your boot loader
The link /initrd.img.old is a damaged link
Removing symbolic link initrd.img.old
You may need to re-run your boot loader
Purging configuration files for linux-image-2.6.39-1-686-pae ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 2.6.39-1-686-pae /boot/vmlinuz-2.6.39-1-686-pae
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 2.6.39-1-686-pae /boot/vmlinuz-2.6.39-1-686-pae
OK, it seems that got fixed, ls -l shows
initrd.img -> /boot/initrd.img-2.6.39-1-486...
OK, so it seems I finally made the transition. Just hope it boots...
--- End Message ---
--- Begin Message ---
Source: ldc
Source-Version: 0.13.0alpha1-1
We believe that the bug you reported is fixed in the latest version of
ldc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 627566@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Konstantinos Margaritis <markos@debian.org> (supplier of updated ldc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 14 Feb 2014 14:19:56 +0200
Source: ldc
Binary: ldc
Architecture: source amd64
Version: 0.13.0alpha1-1
Distribution: unstable
Urgency: medium
Maintainer: Arthur Loiret <aloiret@debian.org>
Changed-By: Konstantinos Margaritis <markos@debian.org>
Description:
ldc - LLVM D Compiler
Closes: 625037 627566 654605 707372 726910 730782 730798
Changes:
ldc (0.13.0alpha1-1) unstable; urgency=medium
.
* New upstream release. Closes: #726910.
* New maintainer Closes: #730798.
* Fixes lots of FTBFS bugs. Closes: #625037, #627566, #707372, #654605, #730782.
Checksums-Sha1:
a1edc87fb12d07ecbe8f6748da017ce6a477f49e 1868 ldc_0.13.0alpha1-1.dsc
26794926e05bdfb3a3266a13cb241de2c44aa862 3179248 ldc_0.13.0alpha1.orig.tar.xz
917518d9464a0f7182c8d73121cec92fd6d91f60 11956 ldc_0.13.0alpha1-1.debian.tar.xz
c75c5151652d29fe4cb3ef89009e6e89a4dc3769 12831122 ldc_0.13.0alpha1-1_amd64.deb
Checksums-Sha256:
f90c2e9ba99957d15b1b9f52cdde20ce9ca4a450d5f7c36e185c8fb6eff78873 1868 ldc_0.13.0alpha1-1.dsc
9871c01ea2b9627b7fbb26bd2288cceaba87d8816c87f45cc7386be9f1f3ae5f 3179248 ldc_0.13.0alpha1.orig.tar.xz
24fbb2f95a73730110157cea287b0bbc01109abcbcd727cabf03fba4d7b18d33 11956 ldc_0.13.0alpha1-1.debian.tar.xz
30c434b66cad456d78ffcaa6cdfd572ae329123791a8b64176de6d07d9e7504f 12831122 ldc_0.13.0alpha1-1_amd64.deb
Files:
32f6a871dd2c6ddfafe818f1e47d73ae 1868 devel extra ldc_0.13.0alpha1-1.dsc
05515a53f14e56d32232fd26635d60e9 3179248 devel extra ldc_0.13.0alpha1.orig.tar.xz
23211ffe62a3a6df8f9ce3de3d8a52c4 11956 devel extra ldc_0.13.0alpha1-1.debian.tar.xz
ca14fe213b843991d1fae9df9ab1db86 12831122 devel extra ldc_0.13.0alpha1-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJTAhgeAAoJEGYGAn9kNxJMgiwP+wfp2VFYktLOBTmx8EPOvXv5
eUV/IldMHv1ImI77s7I/30UrCJno8l5qzkBY0jcC94M1p38b6nnJJzDRINiBwKUi
DnE4x7RnCLFyff5g35+voXIXaRaMMk1UsJ3LbaS8l0B0b/el0vPRQY2SYbnQaXnX
7LYck1K5SUFRHC00famvzPVGxLRylFWuIbayq2oobRH6PRK1727F/CudvjunipFG
wnqtQVD51DWJqYKPxjHMsCyTcqtwiSWdYkhTFnST7DVrwgf68Yn/IgyatwMNgzcy
pPH+NM6EvoIK6CX36Mh86V0N0L5ta3OBvlGUUzncUJfYzIEDerrDkb0zpF90hCBL
0cwg1mGitZE/cD4+RU0DUrifZH76yBy5Bym5gARottHUxY+xUfpU4naGMEYuiSPd
PfQgl5UPAU2x+FF2TIk6dLRt3VaiC/3mGuipzDxCYXPMPB8dx9he2B675MPlJDtt
UsQW9wseydjTnW8HsFyqKv3bAy+7id03Na8N2OajR/mmdtB4j9lb2wi5Lwp1ldWi
8v+4P3jybL7tc9rtknAoJ6Ua2x2wpTQTcpMEqGzkSal5JfWCMTgt7HeoiyaHRhpW
5a+g3tHnFhthbQZALdTvnhC+6akthx//Mqzlc4q5VRcyA2uG1txX4Bwmlt6edRRy
OUdLGyVgiWHSWRfLlw7c
=lxOQ
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: