Re: [Duplicity-talk] issues with exporting backups

[Scott Hannahs]

Mac uses a path separator of /.  If in the GUI you put a slash in the file name 
the unix/POSIX layer sees the file name having a colon.

So in the GUI I have a file or folder in my home directory with the name "Data 
3/2014" this shows up as a file to the unix/POSIX layer as "/Users/sth/Data\ 
3\:2014" in shell escape notation.

So the basic question is if duplicity actually puts a colon in the file name or 
properly escapes it?  As far as I can tell the shell escapes the colon but 
doesn't need to since I can reference the file appropriately without the escape 
of the colon "/Users/sth/Data\ 3:2014"

The gui just translates the colon to a slash for display in the finder.  Colons 
are not allowed in file name sin the finder since they translate to a slash 
which is the path separator.  Why is duplicity just removing the whole thing as 
a tilde is the question.

-Scott


On Mar 18, 2014, at 09:38, address@hidden wrote:

> Mac OS used to have colon ':' as path separator in the versions before OSX. 
> they probably hacked a compatibility layer for users still wanting to use 
> slashes in the file names.
> 
> ..ede
> 
> On 18.03.2014 14:33, Kenneth Loafman wrote:
>> Not sure how you can have slashes in a filename... what's the path separator?
>> 
>> On Tue, Mar 18, 2014 at 8:02 AM, Quinn Shanahan <address@hidden 
>> <mailto:address@hidden>> wrote:
>> 
>>    Cool, thanks for your help! I'll file a bug report. I'd be happy to fix 
>> it too, any advice at a place in the code to start looking would be great. 
>> 
>>    Quinn
>> 
>> 
>>    On Tue, Mar 18, 2014 at 7:55 AM, <address@hidden <mailto:address@hidden>> 
>> wrote:
>> 
>>        On 18.03.2014 12:53, Quinn Shanahan wrote:
>>> Hi, I experienced two issues while "checking out" my backup:
>>> 
>>> 1. All the timestamps were reset. I read online that this could be because 
>>> the target does not have the user / groups the original machine did. I 
>>> don't really care about preserving the original user and groups, but I do 
>>> want the timestamps. Is there any workaround for this?
>> 
>>        restore as root. duplicity can restore file attributes only as 
>> superuser somehow. dunno why.
>> 
>>> 2. OS X allows slashes (/) in filenames (they read as colons when printed 
>>> in the terminal). When duplicity creates the file, it gives it a name like: 
>>> AGO2OZ~A.DOC when the orginal filename was something like "ago / 
>>> something.doc".
>>> 
>>> any help is greatly appreciated! I apologize if I overlooked something in 
>>> the doc that would explain this.
>>> 
>> 
>>        that's probably a bug in duplicity, which probably occurs rarely 
>> because of the few mac users + the idea to name files like that. please file 
>> a bug at launchpad but do not expect someone to jump at solving it.
>> 
>>        ..ede/duply.net <http://duply.net>