Florian Kulzer wrote:
On Thu, Sep 03, 2009 at 19:06:41 +0200, Bernard wrote:
Florian Kulzer wrote:
On Thu, Sep 03, 2009 at 00:09:07 +0200, Bernard wrote:
Florian Kulzer wrote:
On Wed, Sep 02, 2009 at 20:26:06 +0200, Bernard wrote:
Before the end of install process, I got
this message :
"
Configuring libc6
[...]
Do you want to upgrade glibc now ?
"
I replied 'no', and, so far, I have not attempted to continue this
install process of 'audacity' and the upgrade of glibc.
[...]
Ever since then, I am encountering problems and error messages when
trying to install something. For instance, if I do :
#apt-get install gphoto2
the install process starts... then :
"
Can't exec "locale": no file or directory of this type at
/usr/share/perl5/Debconf/Encoding.pm line 16.
Use of uninitialized value $Debconf::Encoding::charmap in scalar
chomp at /usr/share/perl5/Debconf/Encoding.pm line 17.
dpkg : « ldconfig » not found in the variable PATH.
dpkg: 1 expected program not found in the variable PATH.
NB : the variable PATH of the superuser should contain
/usr/local/sbin, /usr/sbin et /sbin.
E: Sub-process /usr/bin/dpkg returned an error code (2)
[...]
new-host:/home/bd# dpkg -l libc6\* libc-\* | awk '/^[^D|+]/{print $1,$2,$3}'
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
rc libc-bin 2.9-25
un libc-dev <néant>
ii libc6 2.7-18
ii libc6-dev 2.7-18
ii libc6-i686 2.7-18
un libc6.1 <néant>
[...]
Here is what I get :
file /sbin/ldconfig
/sbin/ldconfig: ERROR: cannot open `/sbin/ldconfig' (No such file or directory)
dpkg -L libc6 | grep ldconfig
(it just returns the shell, nothing else)
It seems that dpkg is confused: It claims that libc6 version 2.7-18 is
installed without problems, but it does not know about /sbin/ldconfig
and the file itself is not present on your system.
r...@new-host:/home/bd# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
That is OK at least.
I propose to try reinstalling libc6 2.7-18 with dpkg. The necessary .deb
file should still be in your apt cache, so this might work:
dpkg -i /var/cache/apt/archives/libc6_2.7-18_*.deb
I will test this right away. Before doing this, so as to make sure I
won't forget later, I am pasting an output below :
b...@new-host:/var/cache/apt/archives$ ls -l libc6*
-r--r--r-- 1 root root 4437976 aoû 26 03:06 libc6_2.7-18_i386.deb
-rw-r--r-- 1 root root 3802420 aoû 17 00:05 libc6_2.9-25_i386.deb
-rw-r--r-- 1 root root 3802602 aoû 31 19:02 libc6_2.9-26_i386.deb
-rw-r--r-- 1 root root 3377088 jan 5 2009 libc6-dev_2.7-18_i386.deb
-rw-r--r-- 1 root root 4802506 aoû 17 00:05 libc6-dev_2.9-25_i386.deb
-rw-r--r-- 1 root root 4803706 aoû 31 19:02 libc6-dev_2.9-26_i386.deb
-rw-r--r-- 1 root root 1234710 aoû 17 00:05 libc6-i686_2.9-25_i386.deb
-rw-r--r-- 1 root root 1234902 aoû 31 19:02 libc6-i686_2.9-26_i386.deb
The file dates are interresting. I have several libc6 packages. The ones
dated aug 31 (libc6_2.9-26_i386.deb and libc6-i686_2.9-26_i386.deb) must
be the ones that tried to get install in the process of installing
'audacity 1.3.8 testing'. The install process clearly stated that it was
going to update my libc6. The only package dated aug 26 must be the one
that got installed in the process of setting up my new Lenny at that
date ; there was no associated dev package. I don't know what are
packages dated aug17, since it was a few days before I installed Lenny ;
at the time I was still running Sarge and, since I did not upgrade but
reformated and installed from scratch, I should have no remains from old
Sarge in my system. What is puzzling me is that the package dated aug 16
is of a newer version than the one dated aug 26. An other thing that
come to my attention is that all of these deb package files are 'rw',
except the first one that appears on the list, dated aug26, the date of
my Lenny install.
This being said, I will be trying to re-install libc6. Coming back soon.
If the .deb is missing then you can download it manually with your
favorite browser:
http://packages.debian.org/lenny/libc6
(Scroll down to the section "Download libc6" and click on the link for
your architecture in the table.)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
