This is reroducible with the simple test case below: [EMAIL PROTECTED]:/tmp# mkdir -p foo/bar/baz [EMAIL PROTECTED]:/tmp# touch foo/bar/baz/ungh [EMAIL PROTECTED]:/tmp# rm -rf foo/ rm: cannot remove `foo/bar': Function not implemented
** Changed in: coreutils (Ubuntu) Sourcepackagename: dpkg => coreutils ** Changed in: coreutils (Ubuntu) Importance: Undecided => High ** Bug watch added: Debian Bug tracker #464118 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464118 ** Also affects: coreutils (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464118 Importance: Unknown Status: Unknown ** Summary changed: - dpkg shouldn't require /proc to be mounted + rm shouldn't require /proc to be mounted ** Description changed: - Binary package hint: dpkg + Binary package hint: coreutils When upgrading the buildd chroot tarballs, I got errors such as: rm: cannot remove `/var/lib/dpkg/tmp.ci/control': Function not implemented dpkg: error processing /var/cache/apt/archives/dash_0.5.4-6ubuntu1_ia64.deb (--unpack): subprocess rm cleanup returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/dash_0.5.4-6ubuntu1_ia64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Mounting /proc and trying again seemed to resolve the issue, but this is the first time I've ever seen such behavior. In the past, I've filed (and fixed) bugs on packages in base that would - bomb out if /proc wasn't mounted, so it seems to be a regression that - our packaging system itself now depends on /proc. + bomb postinsts if /proc wasn't mounted, so it seems to be a pretty nasty + regression that coreutils now depends on /proc. -- rm shouldn't require /proc to be mounted https://bugs.launchpad.net/bugs/192239 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
