v1.60 is very old indeed. Not sure why you bring it on this forum:) It is not rclone problem, isn't it? Rclone team does not maintain any Linux distros rclone distribution channels.
So contact your Linux distro maintainers and get involved trying to make it up to date. You can also switch to another Linux where programs are updated in more timely manner. Personally I recommend Suse Tumbleweed. Or live with what you've got.
Otherwise uninstall it and install the latest one from here.
Sorry and thanks for replying, this is my first post. Should I ask these kinds of questions elsewhere?
I'm unsure if that flag is unsupported in that version or if it's some other problem like mixing parameters or the backend compatibility is the issue?
It's impossible to change the os or install a version not sourced from a trusted repo. That raises another question.
Are there any plans to provide a repo.rclone.org to source tested installations from?
None of those installation processes are compatible with the default package management tools for most major linux distros. They introduce additional knowledge and automation requirements to maintainers of those systems.
I do not think so. But if you feel like doing and maintaining it then you are more than welcomed. People will help you for sure in this endeavour.
Correct. At the same time as rclone does not have any dependencies it does not risk messing up with anything.
It is your call what you do. I already told you available options IMO.
And really if you want to 100% rely on your Linux distro packaging then Debian is probably the worst choice possible:) Using old but rock solid stable software has its advantages some people need - mostly when running servers. For workstation it is not the best choice.
Sorry if you felt that my reply is a bit harsh but your question is rather about Debian repository not rclone. So Debian forums are where people discuss it:)
I'm not sure why this became a distro bash. It's obvious from a marketing perspective that if you want any product to be accepted by the wider community, you need to make it easily accessible mainstream. Anyway, that wasn't my question.
I want to know if the problem I'm seeing is compatibility or configuration related?
What I gather from your responses is that you suspect it's compatibility related but aren't bothered to look at it and would rather bang on about distros