Comment 1 for bug 1955347

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
I'm not 100% sure but to me that is a setup and configuration issue with the new version being a bit more insisting that it can read/access paths it is supposed to back up.

The new behavior can be disabled with --ignore-errors, but I'm tempted to consider this dangerous as you could have any other I/O error and it would still delete things.

Did you try to use --exclude=PATTERN and if that matches your use case --delete-excluded to make the new version behave as you were used from the older one?