rm shouldn't require /proc to be mounted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
coreutils (Debian) |
Fix Released
|
Unknown
|
|||
coreutils (Ubuntu) |
Won't Fix
|
High
|
Unassigned | ||
Hardy |
Won't Fix
|
High
|
Unassigned |
Bug Description
Binary package hint: coreutils
When upgrading the buildd chroot tarballs, I got errors such as:
rm: cannot remove `/var/lib/
dpkg: error processing /var/cache/
subprocess rm cleanup returned error exit status 1
Errors were encountered while processing:
/var/cache/
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 postinsts if /proc wasn't mounted, so it seems to be a pretty nasty regression that coreutils now depends on /proc.
description: | updated |
Changed in coreutils: | |
status: | Unknown → New |
Changed in coreutils: | |
assignee: | nobody → james-w |
Changed in coreutils: | |
status: | New → Won't Fix |
Changed in coreutils: | |
status: | New → Confirmed |
Changed in coreutils (Debian): | |
status: | Won't Fix → Fix Released |
This is reroducible with the simple test case below:
root@ross:/tmp# mkdir -p foo/bar/baz
root@ross:/tmp# touch foo/bar/baz/ungh
root@ross:/tmp# rm -rf foo/
rm: cannot remove `foo/bar': Function not implemented