Re: [Duplicity-talk] restoring timestamps

[Andre Ruiz]

The problem with changing the group after changing the permissions is
that attributes like g+s attribute get reset. The current order seems
correct, so the alternative would be to catch the exception.

andre

On Apr 1, 2005 2:22 PM, Seb Wills <address@hidden> wrote:
> 
> When I try to restore a backup of another user's files, naturally
> duplicity is unable to restore the correct owner to the files, giving
> "Error '[Errno 1] Operation not permitted: ...". But this situation also
> seems to prevent it from restoring the modification timestamps. Is this by
> design, or by accident?
> 
> In my opinion it would make sense for duplicity to restore the archived
> timestamps even if it cannot restore the correct file ownership.
> 
> My quick hack to effect this enhancement is to move the call to
> os.chown(), which is throwing the error, in path.py, to below the calls to
> os.utime() and os.chmod(). I guess a neater solution would be to catch the
> exception, print a helpful message, and continue the normal flow of
> execution.
> 
> seb
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 


-- 
Andre Ruiz  <address@hidden>
Curitiba, PR, Brasil