Bug#365397: marked as done (sed used but no in dependency list)
Your message dated Thu, 18 May 2006 03:03:20 +0000
with message-id <446BE3F8.3080209@aurel32.net>
and subject line Bug#365397: sed used but no in dependency list
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libc6
State: partially configured
Automatically installed: no
Version: 2.3.2.ds1-22sarge3
Priority: required
Section: base
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Uncompressed Size: 15.7M
Depends: libdb1-compat
Suggests: locales, glibc-doc
Install libc6 fails because(?) no sed was installed but seems to
be used in libc6.postinst.
/# aptitude install libc6
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following packages have been kept back:
libgnutls11 libtasn1-2 tar
The following packages will be upgraded:
libc6
1 packages upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 0B/4914kB of archives. After unpacking 184kB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "C",
LC_ALL = (unset),
LC_CTYPE = "de_DE@euro",
LANG = (unset)
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... 7492 files and directories currently installed.)
Preparing to replace libc6 2.3.2.ds1-22 (using .../libc6_2.3.2.ds1-22sarge3_i386.deb) ...
/var/lib/dpkg/tmp.ci/preinst: line 1: sed: command not found
dpkg: error processing /var/cache/apt/archives/libc6_2.3.2.ds1-22sarge3_i386.deb (--unpack):
subprocess pre-installation script returned error exit status 127
/var/lib/dpkg/info/libc6.postinst: line 1: sed: command not found
dpkg: error while cleaning up:
subprocess post-installation script returned error exit status 127
Errors were encountered while processing:
/var/cache/apt/archives/libc6_2.3.2.ds1-22sarge3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Ack! Something bad happened while installing packages. Trying to recover:
Setting up libc6 (2.3.2.ds1-22) ...
Current default timezone: 'Europe/Berlin'.
Local time is now: Sat Apr 29 20:52:49 CEST 2006.
Universal Time is now: Sat Apr 29 18:52:49 UTC 2006.
Run 'tzconfig' if you wish to change it.
/var/lib/dpkg/info/libc6.postinst: line 1: sed: command not found
grep: write error: Broken pipe
dpkg: error processing libc6 (--configure):
subprocess post-installation script returned error exit status 127
Errors were encountered while processing:
libc6
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Rainer---<=====> Vertraulich
//
//
<=====>--------------ocholl, Kiel, Germany ------------
--- End Message ---
--- Begin Message ---
Rainer Zocholl wrote:
aurelien@aurel32.net(Aurelien Jarno) 17.05.06 04:07
Rainer Zocholl wrote:
liw@liw.iki.fi(Lars Wirzenius) 29.04.06 23:15
la, 2006-04-29 kello 20:56 +0200, Rainer Zocholl kirjoitti:
Install libc6 fails because(?) no sed was installed but seems to
be used in libc6.postinst.
sed is essential, so always guaranteed to be there:
liw@agnes$ dpkg --status sed
Package: sed
Essential: yes
Thanks.
But the "sed" command is not working anymore.
I can do an
#ls /bin/sed
which gives:
sed
but a
#ls -al /bin/sed
gives:
ls: /bin/sed: No such file or directory
It looks like your filesystem is totally screwed. Please do a fsck to
fix that, and maybe reinstall the packages that are screwed.
Yes. you'r right. It was a vserver with some broken hardlinks
(not all, that's the problem).
So there is no bug in the glibc...
That leads to an other question:
Should such an important and powerful programm like
an installer not check if all required tools are really there and runable?
Assume a wrong selective chmod -R 644 ...
or a "mv" which moves that seldom used tool away
there are thoundsand of ways.
Maybe, but this is not a problem in the glibc, closing the bug.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian GNU/Linux developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---
Reply to: