Bug#365647: Does libc6 2.3.6-7 break Sarge
Petr wrote: Hi, it seems related to #364338, #364516. There is LD_ASSUME_KERNEL=2.4 in sarge version of /usr/sbin/mkinitrd. Could you downgrade your initrd-tools to sarge version and change it into LD_ASSUME_KERNEL=2.4.1. Does it help ? Petr smtp:~# uname -r 2.4.27-3-586tsc smtp:~# apt-cache policy initrd-tools initrd-tools: Installed: 0.1.81.1 Candidate: 0.1.81.1 Version table: 0.1.84.1 0 650 http://mirrors.kernel.org testing/main Packages *** 0.1.81.1 0 990 http://mirror.cs.wisc.edu stable/main Packages 100 /var/lib/dpkg/status Before the change: smtp:~# mkinitrd -o /boot/temp 2.4.27-3-686 /bin/bash: error while loading shared libraries: libdl.so.2: \ cannot open shared object file: No such file or directory After the change: smtp:~# mkinitrd -o /boot/temp 2.4.27-3-686 /bin/bash: error while loading shared libraries: libdl.so.2: \ cannot open shared object file: No such file or directory grep: error while loading shared libraries: libc.so.6: \ cannot open shared object file: No such file or directory sort: error while loading shared libraries: libc.so.6: \ cannot open shared object file: No such file or directory awk: error while loading shared libraries: libm.so.6: \ cannot open shared object file: No such file or directory I also changed LD_ASSUME_KERNEL=2.4 to LD_ASSUME_KERNEL=2.4.1 in /usr/share/initrd-tools/scripts/e2fsprogs and then was able to create an initrd.img without the error. It appears it is required to change it in both places. Gary V -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365647: Does libc6 2.3.6-7 break Sarge
I see where the initrd-tools maintainer(s) has marked this as fixed but I don't see any updated packages. I wrote myself a dirty little script that could be used to fix this (at least it does what I need it to). http://www200.pair.com/mecham/fix.mkinitrd Gary V -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#364490: 'dpkg-reconfigure locales' does not update /etc/environment
* Locale variables are now stored in /etc/default/locale and no more /etc/environment. The reason is that Debian Policy forbids modifying configuration files of other packages, and /etc/environment is a configuration file for PAM. Make sure to remove old definitions from /etc/environment, this file is no more modified for the reason explained above. OK, thank you. Gary V -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365647: error while loading shared libraries Does libc6 2.3.6-7 break Sarge?
Package: libc6 Version: 2.3.6-7 I am somewhat of a noob so I hope I'm in the right place (and not totally off base). I installed Debian Sarge with the i386 2.4.27 kernel. I use 'stable' for most of my system but install a few packages from 'testing'. I installed a program from testing (mdadm) that brought libc6 version 2.3.6-7 along with it. Now I cannot run some programs, for example: ~# mkinitrd -o temp 2.4.27-3-686 /bin/bash: error while loading shared libraries: libdl.so.2: \ cannot open shared object file: No such file or directory I thought this might be because the new libc6 is not compatible with older kernels, so, as a test I installed sarge kernel 2.6.8: apt-get install kernel-image-2.6.8-2-386 but this did not help. So I tried installing: apt-get install linux-image-2.6.15-1-486 (Note: In my experience migrating from kernel-image kernels to linux-image kernels tends to break RAID.) but I still get the same error. I think this problem may break a lot of systems. As another test I upgraded initrd-tools to the 'testing' version and got these errors: mkinitrd -o temp 2.4.27-3-686 /bin/bash: error while loading shared libraries: libdl.so.2: \ cannot open shared object file: No such file or directory sort: error while loading shared libraries: libc.so.6: \ cannot open shared object file: No such file or directory awk: error while loading shared libraries: libm.so.6: \ cannot open shared object file: No such file or directory grep: error while loading shared libraries: libc.so.6: \ cannot open shared object file: No such file or directory As a final test, I did an: apt-get -t testing dist-upgrade (which I had problems with - had to install x11-common with force overwrite). During the dist-upgrade, because of this same error: Using /usr/sbin/mkinitrd to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd \ /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. /bin/bash: error while loading shared libraries: libdl.so.2: \ cannot open shared object file: No such file or directory grep: error while loading shared libraries: libc.so.6: \ cannot open shared object file: No such file or directory sort: error while loading shared libraries: libc.so.6: \ cannot open shared object file: No such file or directory awk: error while loading shared libraries: libm.so.6: \ cannot open shared object file: No such file or directory Trying to upgrade the kernel once again resulted in this: Could not find mkinitramfs-kpkg mkinitrd.yaird. at /var/lib/dpkg/tmp.ci/preinst \line 236, STDIN line 9. Done. Setting up linux-image-2.6.15-1-686 (2.6.15-8) ... Running depmod. Finding valid ramdisk creators. Failed to find suitable ramdisk generation tool for kernel version 2.6.15-1-686 on running kernel 2.4.27-3-586tsc in mkinitramfs-kpkg mkinitrd.yaird Any simple way to fix this issue? Gary V -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#364490: 'dpkg-reconfigure locales' does not update /etc/environment
Package: locales Version: 2.3.6-7 I thought answering the prompt: Default locale for the system environment: would change the LANG variable in /etc/environment as it appears to do in version 2.3.5-6 which I have installed in another (Sarge) machine. Using the 2.3.6-7 version, I can't see that it ever touches the file. Using Debian Etch beta2 CD kernel 2.6.15-1-486 Gary V -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
