Re: [Duplicity-talk] issues with exporting backups

[Scott Hannahs]

Yes that would be my read, but not knowing duplicity or rather python path 
conventions it is a SWAG (Scientific Wild A$$ Guess).

Having a forward slash "/" in a file name is not "confusing" but more strictly 
forbidden by the OS, so it is a little bit stronger but is the standard unix 
type restriction.

So what does python/duplicity do with a filename containing a colon ":" ?

-Scott

On Mar 18, 2014, at 12:55, Quinn Shanahan <address@hidden> wrote:

> Exactly, the gui always displays colons as slashes, and disallows colons from 
> being entered into filenames from the gui (because they would end up being 
> shown as slashes, which I guess would be confusing). Which means that if the 
> archives store as a colon and export as a colon, it is 1 to 1 compatible with 
> OS X. on ubuntu it will show a colon, and when moved back to OSX it will be a 
> slash. So, as you're saying, I think the issue here is that duplicity is 
> having trouble with a file that has a colon in it, not anything to do with OS 
> X. 
> 
> Quinn