Your message dated Fri, 24 Oct 2014 09:04:33 -0400
with message-id <[email protected]>
and subject line Re: rm -r broken: Function not implemented (using coreutils 
6.10 with a pre-etch kernel)
has caused the Debian Bug report #464118,
regarding rm -r broken: Function not implemented (using coreutils 6.10 with a 
pre-etch kernel)
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 [email protected]
immediately.)


-- 
464118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464118
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: coreutils
Version: 6.10-3
Severity: grave


I installed this package, after which my entire system started to break
due to problems caused in mkinitramfs and packages fail to install.

/var/cache/apt/archives/coreutils_6.10-3_i386.deb

After using a boot CD, chrooting and re-installing 
/root/coreutils_5.97-5.3_i386.deb

rm -r was working as expected again.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (700, 'experimental'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22.1 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages coreutils depends on:
ii  libacl1                      2.2.45-1    Access control list shared library
ii  libc6                        2.7-6       GNU C Library: Shared libraries
ii  libselinux1                  2.0.15-2+b1 SELinux shared libraries

coreutils recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message --- The situation affected something obsolete enough that it's probably safe to just close the bug at this point--I don't think anyone is likely to be running into the problem again.

Mike Stone

--- End Message ---

Reply via email to