Replies: 1 comment 1 reply
-
See: https://download.samba.org/pub/rsync/NEWS#3.2.4 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear all,
I just noted a behaviour change where I am unsure whether this is by design or a bug.
I am using backintime to do backups to a remote server over ssh. backintime generates an elaborated rsync command and runs it. Now my backups stopped working under ubuntu 22.10. I tracked down the problem to a change in the rsync version (22.04: 3.2.3; 22.10: 3.2.5). The commandline generated by backintime is exactly the same.
The command line contains sth like: user@buserver:"/absolute/path/spec" as the target (note that the path is double-quoted). Additionally ssh is used: i.e. "--rsh=ssh -o ..."
The final directory (e.g. spec) does not exist yet, so rsync tries to create it.
With rsync3.2.3 this is working just fine, whereas with 3.2.5, rsync tries to create a directory that looks like $HOME"/absolute/path/spec" (e.g. /home/user/"/absolute/path/spec").
This $HOME-path is exactly the (absolute) path the user ends up in when connecting via ssh.
Coming back to my question... is this a bug or a feature?
Thanks for any hint, Raph
Beta Was this translation helpful? Give feedback.
All reactions