Your message dated Thu, 18 May 2006 03:03:20 +0000
with message-id <[EMAIL PROTECTED]>
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 <[email protected]>
Uncompressed Size: 15.7M
Depends: libdb1-compat
Suggests: locales, glibc-doc
Install libc6 fails because(?) no sed was installed but sed
seems to be used in libc6.postinst.
sed can't be installed anymore because libc6 is partly installed
and can't be removed without removing the entire base system...
Pardon, that's not a libc6 specifc problem.
sed IS installed
sed IS in /bin/
/bin is in PATH...
but:
Tha might be a problem of sym links?
:/# ls /bin | grep sed
sed
See the "sed" ?
:/# ls -al /bin | grep sed
ls: /bin/mount: No such file or directory
ls: /bin/umount: No such file or directory
ls: /bin/sed: No such file or directory
ls: /bin/arch: No such file or directory
ls: /bin/more: No such file or directory
ls: /bin/dmesg: No such file or directory
ls: /bin/loadkeys: No such file or directory
ls: /bin/fgconsole: No such file or directory
ls: /bin/ping: No such file or directory
ls: /bin/ping6: No such file or directory
:/# ls -al /bin/s*
ls: /bin/sed: No such file or directory
lrwxrwxrwx 1 root root 15 Apr 14 23:35 /bin/setpci -> /usr/bin/setpci
lrwxrwxrwx 1 root root 4 Apr 14 23:34 /bin/sh -> bash
-rwxr-xr-x 10 root root 14424 Jul 16 2004 /bin/sleep
-rwxr-xr-x 10 root root 36856 Jul 16 2004 /bin/stty
-rwsr-xr-x 10 root root 23416 May 18 2005 /bin/su
-rwxr-xr-x 10 root root 12216 Jul 16 2004 /bin/sync
:/# aptitude show sed
Package: sed
Essential: yes
State: installed
Automatically installed: no
Version: 4.1.2-8
--- End Message ---
--- Begin Message ---
Rainer Zocholl wrote:
[EMAIL PROTECTED](Aurelien Jarno) 17.05.06 04:07
Rainer Zocholl wrote:
[EMAIL PROTECTED](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:
[EMAIL PROTECTED] 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
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---
