Dear Maintainer,

I was trying to rsync my server to my desktop as a backup today, running
testing on my desktop and stable on the server. First my script failed
due to --noatime being renamed to --open-noatime, easily fixed. Then it
failed because the server doesn't know about --open-noatime:

  rsync: on remote machine: --open-noatime: unknown option

Easiest "fix" for now seems to be accepting "--noatime" on newer
versions and deprecate it when "--open-noatime" is more widely spread.

Installing rsync from buster-backports on my servers helped as a
workaround for now.

Best regards, thank your for your work and have a happy new year (if
your calendar overflows this night)
Mara Sophie Grosch

(second try, reportbug not configured on this machine x.x)

Hello Mara,

Thanks for reporting the issue,

Unfortunately this was an expected behavior, upstream changed the
parameter as the previous one was not part of the official release (it
was an upstream provided patch), I haven't looked into the details yet
to know if a compatibility patch can be provided but if so, I suggest
contacting upstream.

I'm happy to know that the backports package was useful :)

Thanks,

Hello,

based on the comments and new releases since this ticket was opened, it
seems the issue is not relevant anymore.

Any objects against closing it?

Regards,
Christian Buhtz