basak

> the new glacier-cli script name Ah, that was inadvertent. Relevant here is #30, #47 and #57. Note that I also want to coordinate with git-annex so we don't break...

Thank you for the pip instructions though - they look fine and I'm happy to merge that as soon as we sort out what we're doing with the name.

Thanks! > I’d be happy to help with the name update as well, once you know what you want to do. I'd like to: 1. [Edit] Check that the name...

Thank you for the report. Maybe it would be easiest to "deep link" directly into the git history instead - for example to http://source.git-annex.branchable.com/?p=source.git;a=blob;f=doc/bugs/Glacier_remote_uploads_duplicates.mdwn;h=75014a5e049a397cef2dd8745e98d4094319e1f6;hb=a9c7260adb7f6336270fe1af90484abb3bbb3991 - plus all the comments?

I'd like this, but as you've identified #30 probably needs to be resolved first.

Thanks! This looks like a bug in boto (the underlying AWS access library) and I'll follow the bug up there when I can.

Right. I filed https://github.com/boto/boto/issues/1548, but that's as far as I got. It seems a bit onerous to use a different name in this project since it's designed for direct command...

I like `glcr`. I hadn't consider that before and missed it in winny-'s, sorry. And this has gone unresolved for long enough. Provided the name's not already taken (someone please...

> I don't think git-annex should be hardcoding the executable name anyway. I have no issue with that. But we should have a single well-known name that everything that expects...

What would you prefer to see instead? distutils? setuptools? Something else?