From 85624015978b0de294cff3df79006df987c552b1 Mon Sep 17 00:00:00 2001 From: Lasse Collin Date: Tue, 25 Oct 2022 18:23:54 +0300 Subject: xz: If input file cannot be removed, treat it as a warning, not error. Treating it as a warning (message + exit status 2) matches gzip and it seems more logical as at that point the output file has already been successfully closed. When it's a warning it is possible to suppress it with --no-warn. --- src/xz/file_io.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src') diff --git a/src/xz/file_io.c b/src/xz/file_io.c index 6fa847e2..b559ae35 100644 --- a/src/xz/file_io.c +++ b/src/xz/file_io.c @@ -330,14 +330,14 @@ io_unlink(const char *name, const struct stat *known_st) // it is possible that the user has put a new file in place // of the original file, and in that case it obviously // shouldn't be removed. - message_error(_("%s: File seems to have been moved, " + message_warning(_("%s: File seems to have been moved, " "not removing"), name); else #endif // There's a race condition between lstat() and unlink() // but at least we have tried to avoid removing wrong file. if (unlink(name)) - message_error(_("%s: Cannot remove: %s"), + message_warning(_("%s: Cannot remove: %s"), name, strerror(errno)); return; -- cgit v1.2.3