yorkday

After reading through the closed issues, I saw part of my issue has been raised before: https://github.com/laurent22/rsync-time-backup/issues/84 I agree with @laurent22 that it is too difficult to parse rsync errors...

Looks like destination folder and log names are handled separately which is causing the problem. One interpretation is that the log is definitely created at a later time in the...

Agreed. The $NOW variable might need to be defined and moved earlier in the code to be safe, otherwise in future if you included additional logging before creating the destination...

I don't understand this reasoning. There is nothing special about the first backup, it is just a backup point. You can prune any backup, and all remaining backup points are...

I appreciate you fixing the pruning logic which was not working, but this feature that works for you, means the backup strategy now does not work as specified. I think...

By keeping the first backup to save users and make it "fool proof", I think you're perpetuating the perception that the backup is an archive mechanism, when it's not. Keeping...

Just confirming this is still an open issue. Workaround suggested above by @SimonHeimberg does workaround, but code should still be fixed to prune as per command (it should not assume...