[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34700: rm refuses to remove files owned by the user, even in force m
From: |
Nicolas Mailhot |
Subject: |
bug#34700: rm refuses to remove files owned by the user, even in force mode |
Date: |
Fri, 01 Mar 2019 13:48:51 +0100 |
User-agent: |
Evolution 3.31.91 (3.31.91-1.fc30) |
Hi,
For their own reasons, the Go maintainers have decided the user Go cache
will now be read-only.
https://github.com/golang/go/issues/27161#issuecomment-433098406
That means cleaning up cache artefacts with rm does not work anymore
https://github.com/golang/go/issues/30502
I understand the need to protect read only files (even though they're
supposed to have been created by a user decision, not by user-hostile
tools). However should not rm remove the files anyway in force (-f) mode
without an explicit chmod first? Do it without bothering me is why -f
exists after all.
$ rpm -q --whatprovides /usr/bin/rm
coreutils-8.30-9.fc30.x86_64
Best regards,
--
Nicolas Mailhot
- bug#34700: rm refuses to remove files owned by the user, even in force mode,
Nicolas Mailhot <=
- bug#34700: rm refuses to remove files owned by the user, even in force mode, Eric Blake, 2019/03/01
- bug#34700: rm refuses to remove files owned by the user, even in force mode, Bob Proulx, 2019/03/02
- bug#34700: rm refuses to remove files owned by the user, even in force mode, Erik Auerswald, 2019/03/02
- bug#34700: rm refuses to remove files owned by the user, even in force mode, Bob Proulx, 2019/03/02
- bug#34700: rm refuses to remove files owned by the user, even in force mode, L A Walsh, 2019/03/03
- bug#34700: rm refuses to remove files owned by the user, even in force mode, Erik Auerswald, 2019/03/03
- bug#34700: rm refuses to remove files owned by the user, even in force mode, L A Walsh, 2019/03/03
- bug#34700: rm refuses to remove files owned by the user, even in force mode, Nicolas Mailhot, 2019/03/04