From: Michael Albinus <michael.albinus@gmx.de>
To: Jean Louis <bugs@gnu.support>
Cc: 58132-done@debbugs.gnu.org
Subject: bug#58132: 29.0.50; Tramp: not preserving remote chmod attributes when copy
Date: Mon, 07 Nov 2022 11:40:11 +0100 [thread overview]
Message-ID: <87zgd3m4j8.fsf@gmx.de> (raw)
In-Reply-To: <87leowjsur.fsf@gmx.de> (Michael Albinus's message of "Mon, 31 Oct 2022 09:32:44 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Jean,
>> Normal behavior with local `copy' command is to preserve attributes of
>> the destination file, if such file exists.
>>
>> Normal behavior of ssh/scp is to preserve file attributes of destination
>> file if such file exists:
>>
>> $ ssh stw1 ls -l /home/admin/diff.sql
>> -rwxr-xr-x 1 admin admin 6240 Sep 27 20:22 /home/admin/diff.sql
>> ~
>> $ ls -l diff.sql
>> -rw-r--r-- 1 admin admin 6240 Jun 20 2021 diff.sql
>> ~
>> $ scp diff.sql stw1:~/
>> diff.sql 100% 6240 20.6KB/s 00:00
>> ~
>> $ ssh stw1 ls -l /home/admin/diff.sql
>> -rwxr-xr-x 1 admin admin 6240 Sep 27 20:23 /home/admin/diff.sql
>> ~
>>
>> I have noticed that Tramp transfers file attributes from local file to
>> remote file. This causes server errors, as it is out of the habit that
>> file attributes on existing file are to be preserved.
>
> Tramp does what it is instructed. Copying a file is triggered by the
> `copy-file' function. If the argument PRESERVE-PERMISSIONS is non-nil,
> Tramp tries to preserve the permissions. See the docstring of `copy-file':
>
> So it isn't an error per se.
No further comment, I'm closing the bug therefore.
Best regards, Michael.
prev parent reply other threads:[~2022-11-07 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 3:25 bug#58132: 29.0.50; Tramp: not preserving remote chmod attributes when copy Jean Louis
2022-10-31 8:32 ` Michael Albinus
2022-11-07 10:40 ` Michael Albinus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgd3m4j8.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=58132-done@debbugs.gnu.org \
--cc=bugs@gnu.support \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).