#536750 option to not chmod() on destination at all

Package:
rdiff-backup
Source:
rdiff-backup
Description:
remote incremental backup
Submitter:
martin f krafft
Date:
2021-09-29 02:27:04 UTC
Severity:
wishlist
#536750#5
Date:
2009-07-13 08:31:53 UTC
From:
To:
rdiff-backup has the ability to store metadata separately, e.g. in
case the destination filesystem does not support metadata or the
user does not have permission to chown() etc.

However, it also still chown()'s and chmod()'s if it can.

It would be nice if there was an option to prevent any sort of
metdata storage on the destination filesystem (and files would only
be created according to the umask).

The reason is that I have a few files and directories with 0000
permissions and those create errors on the destination, when storing
the backups themselves to tape.

It seems a bit counterproductive to store metadata externally but
also insist on using chmod() if possible.
#536750#12
Date:
2020-12-29 23:43:59 UTC
From:
To:
Thank you very much for reporting this error.
 
I would like to ask you if this error is still present in the most
recent versions of rdiff-backup. Currently after a series of
improvements and bug fixes, rdiff-backup is at version 2.0.5

It would be very helpful if you checked again if this bug is still
present. Otherwise we can agree to close the bug,
#536750#17
Date:
2021-09-29 02:24:00 UTC
From:
To:
As this bugs is a request for the upstreamer I open an issue [1] and
forward the request to this bug.

[1] https://github.com/rdiff-backup/rdiff-backup/issues/623