Duplicity

Option to not restore owner

Bug #1211481 reported by CiaranG
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Medium
Unassigned
Duplicity 0.8.15

Bug Description

Unless I'm missing something duplicity always attempts to restore ownership of files, either by user/group name or (using the --numeric-owner option) by uid/gid. Neither of these options is appropriate when attempting to restore to an unrelated machine, and in any case neither is possible unless running as root. Both of these are valid use cases.

There should be an option to simply not attempt this at all. In the 'different machine' case, either of the current options makes a mess. In the 'not root' case, at least everything works properly, but at the expense of an 'operation not permitted' error message spewed out for each and every file.

Revision history for this message
Pedro (pdfrod) wrote :

I'm also affected by this shortcoming. Would be nice if Duplicity had an option to simply ignore the original user/group on restore and assign everything to the current user.

Kenneth Loafman (kenneth-loafman)
Changed in duplicity:
importance: Undecided → Low
Revision history for this message
forevertheuni (forevertheuni) wrote :

I am also affected by this.

My University IT, backed up the data with duplicity. And they decided to create different usernames with different uids. I'm restoring with sudo, and then changing to new user with chown.

Revision history for this message
falloutphil (falloutphil) wrote :

+1 for this - use as root isn't practical and the errors regarding permission changes mask any other potentially important messages in stdout.

Being able to disable this would be very useful.

Kenneth Loafman (kenneth-loafman)
Changed in duplicity:
importance: Low → Medium
milestone: none → 0.8.15
status: New → Fix Committed
Revision history for this message
CiaranG (ciarang) wrote :

Is it really 7 years since I logged this? This is awesome, thanks so much. For anyone driving by and not wanting to hunt it down the new option is --do-not-restore-ownership.

Kenneth Loafman (kenneth-loafman)
Changed in duplicity:
status: Fix Committed → Fix Released
Revision history for this message
Bart Laarhoven (bartgrexx) wrote :

And for everyone driving by after duplicity 2.0.0 was released (like me): this option is now renamed to --no-restore-ownership

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.