New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error backing up SourceTree #30
Comments
Can you give me the output of |
and
|
Can you try this version ? https://github.com/lra/mackup/blob/fix_sourcetree/mackup.py If it breaks anything, just move back your "Application Support/SourceTree" from Mackup to your user's library. |
|
So. I looked at this a bit more...
Nothing really odd there. I'd expect to be able to delete the file. Let's clone the dir and try to delete the file from the OS and see what happens.
Hm. Ok. 'dbingham' has write, so should be able to delete. Am I who I think I am?
Yes, I am. Weird. How about dir permissions. If the dir doesn't have write, I won't be able to delete...
But it does, so that's not it. Only other thing I know of is file flags.
And there it is. "uchg". Weird. I never set that myself. Maybe an earlier version of sourcetree did it automatically? Let's remove it and be sure...
Well, that worked. Let's try it on the real file and try mackup again.
Works like a charm now. |
Thanks that helps I'll work on this |
Could you try the latest version of https://github.com/lra/mackup/blob/fix_sourcetree/mackup.py ? |
you can bring back the sourcetree folder and |
Yeah, it works. But it messes with permissions in a way I wouldn't expect. I would expect permissions to be preserved as much as possible. For example: Before (I put things back as close as possible to the original state):
And the files in the Mackup directory on Dropbox after a
So, I expected the Is that a limitation of Dropbox? |
Also, while I'm thinking about it, is |
For the chmod and xattrs being cleaned up, it's because dropbox uses a default umask of 0644 for files, and when you sync your ssh keys (or any other license) you don't (and can't for ssh) have your key files readable by anyone. As I don't think it make sense for any user config file to be readable by anyone, I just blindly enforce a mode of 0600 to any synced file. The xattrs are cleaned up, because OS X use them to set some ACL that prevent mackup to move some files around too, and I don't see the point of keeping those special ACLs if I 0600 any file. But I might be wrong here. About |
On the permissions changes, I doubt it'll matter for the vast majority of stuff. Maybe someday you'll run across an application that just has to have its xattrs 'just so' in order to work. But until then, I say, go with what you've got. It makes things "cleaner" anyway. I use SourceTree, but I don't know much about how it manages its files. The filename just sounded like it would be something along the lines of a cache of usernames you've used when authenticating with various hostnames. I could be totally wrong. But, in any case, it doesn't sound like anything critical. I could even see an argument for excluding it on purpose for security reasons. Feels weak to me, but I could see it. Anyway, pure speculation on my part. If/when I come across anything definite about this file I'll either open a new ticket or send a pull request your way. For the issue I reported here, I think we're good now. Feel free to close away! Thanks! |
Makes sense, merging in, thx for your help |
The text was updated successfully, but these errors were encountered: