As I understood it, AI was let loose on rsync. This pissed some people off.
At the end of the day it is open source. So the beauty is you can choose for yourself. There is absolutely no need to harass any maintainer ! You can just pick a fork and run it instead. Or stick with the existing rsync project.
@joekamprad the timeshift integration might be broken, a few distros had issues with it.
No disrespect intended towards @huebi at all, but I actually wouldn’t pay too much attention to that linked GitHub “issue” @drunkenvicar.
Developers have opinions, and that thread is largely developers expressing them, sometimes quite colourfully. No actual issue was clearly identified, only a social media post was provided, and fiery anecdotes.
rsync is the underlying tool of many backup/recovery solutions.
Whether you use a graphical frontend like backintimeBackintime restoring fails , timeshift or no frontend at all and just use the command line you might have been affected by a rsync version that contained a bug.
I wasn’t calling you out about anything nor was that my intention. I honestly, naively, just wanted to know what that meant (definition) as far as the tech trade went. Nothing more, nothing less.
I have a pile of rsync scripts as part of my backup infrastructure across four devices and domains. They’re all still working fine. No plans to jump anywhere.