Pádraig Brady wrote:
CH_NOT_APPLIED is smaller than CH_NO_CHANGE_REQUESTED
in the current enum ordering, so we skip this
block as expected for the ignored symlink case.
Sorry, you're quite right; I missed that.
Best wishes,
Chris.
On 25/09/2021 07:07, Chris Webb wrote:
Thanks for the analysis and patch.
I've already pushed a very similar patch at:
https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=e8b56ebd5
Many thanks!
With the above fix, do we also need something like
@@ -300,7 +300,7 @@ process_file (FTS
> Thanks for the analysis and patch.
> I've already pushed a very similar patch at:
> https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=e8b56ebd5
Many thanks!
With the above fix, do we also need something like
@@ -300,7 +300,7 @@ process_file (FTS *fts, FTSENT *ent)
describe
forcemerge 50791 50784
stop
On 24/09/2021 22:16, Chris Webb wrote:
Since bbb19b, chmod has started returning EXIT_FAILURE after skipping a
symlink during a recursive change. This affects chmod in the newly released
coreutils-9.0 vs the previous coreutils-8.32 and older versions:
# mkdir t
Since bbb19b, chmod has started returning EXIT_FAILURE after skipping a
symlink during a recursive change. This affects chmod in the newly released
coreutils-9.0 vs the previous coreutils-8.32 and older versions:
# mkdir t
# cd t
# : > foo
# ln -s foo bar
# chmod-8.32 -v -R u+r . ; echo
