Merge branch 'master' of ssh://git-annex.branchable.com

2 files changed, 79 insertions, 0 deletions

diff --git a/doc/bugs/__39__git_annex_get__39___fails_for_unlocked_files_with_special_characters___40__e.g._umlauts__41___when_using_precompiled_version_6.20160126-g2336107_.mdwn b/doc/bugs/__39__git_annex_get__39___fails_for_unlocked_files_with_special_characters___40__e.g._umlauts__41___when_using_precompiled_version_6.20160126-g2336107_.mdwn
new file mode 100644
index 000000000..b59f7ea94
--- /dev/null
+++ b/doc/bugs/__39__git_annex_get__39___fails_for_unlocked_files_with_special_characters___40__e.g._umlauts__41___when_using_precompiled_version_6.20160126-g2336107_.mdwn
@@ -0,0 +1,76 @@
+### Please describe the problem.
+
+Setup: Centralized bare repository, different clones, annex v6. When files with special characters, for example german umlauts (öäü), are part of the repository, it does not work to get these files if the file is unlocked. It will be successfully downloaded from the repo (the correct file is stored in the .git/annex subfolder), but the textfile with the initial link will not be replaced.  
+
+It seems to be related to the precompiled 6.20160126-g2336107 version, since it works fine for the version packaged for Arch Linux (pacman).
+
+### What steps will reproduce the problem?
+
+
+1) Create a bare repo
+
+    $ git init testing.git --bare --shared
+
+2) clone the bare repo, init
+
+    $ git clone testing.git test1
+    $ git annex init
+    $ git annex upgrade
+
+3) Add some file with umlauts
+
+    $ echo Wäää >> test_öüä
+    $ git add .
+    $ git annex sync --content
+
+4) Clone bare repo again
+
+    $ git clone testing.git test2
+
+5) Init and try to get the file
+
+    $ git annex init 'test3'
+    $ git annex upgrade
+    $ git annex get test_öüä
+
+After the last step the download message will be printed:
+
+    get testäöü (from origin...) 
+    SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
+                  0 100%    0.00kB/s    0:00:00 (xfr#1, to-chk=0/1)
+    (checksum...) ok
+    (recording state in git...)
+
+.. and the file is correctly downloaded, but the file is not replaced and will still contain the file link to the annex folder.
+
+### What version of git-annex are you using? On what operating system?
+
+Failing version:
+
+    $ git-annex version    
+    git-annex version: 6.20160126-g2336107
+
+    build flags: Assistant Webapp Pairing Testsuite S3(multipartupload)(storageclasses) WebDAV Inotify DBus DesktopNotify XMPP ConcurrentOutput TorrentParser Feeds Quvi
+    key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM    URL
+    remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external
+
+
+Working version from Arch Linux:
+
+    git-annex version: 6.20160126
+
+    build flags: Assistant Webapp Pairing Testsuite S3(multipartupload)(storageclasses) WebDAV Inotify DBus DesktopNotify XMPP ConcurrentOutput TorrentParser Feeds Quvi
+    key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM URL
+    remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external
+
+I tested this on two different systems, Arch Linux and Debian Jessie. It does not work with the downloaded precompiled version on both systems.
+
+
+### Please provide any additional information below.
+
+
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+
+Yes, I've been using it for more than a year to synchronize between different PCs. Great work :-) 
+
diff --git a/doc/todo/allow_path-style_semantics_for_S3_bucket_specification.mdwn b/doc/todo/allow_path-style_semantics_for_S3_bucket_specification.mdwn
new file mode 100644
index 000000000..e5e98d112
--- /dev/null
+++ b/doc/todo/allow_path-style_semantics_for_S3_bucket_specification.mdwn
@@ -0,0 +1,3 @@
+It appears that currently there's no way to use the "path-style" method for accessing S3 buckets (as contrasted [here](http://docs.aws.amazon.com/AmazonS3/latest/dev/RESTAPI.html) with the "virtual hosted-style" of bucket specification). Would it be possible to add an S3-special-remote configuration parameter to adjust the underlying S3 library's "s3RequestStyle" config parameter? I believe that the "PathStyle" value would be relevant to this specific request, as mentioned in the [S3 library README](https://github.com/aristidb/aws#frequently-asked-questions).
+
+The virtual-hosted style of bucket specification involves a lot of DNS overhead. In my particular use case, I'm looking at running Ceph with a radosgw with S3 support, and in fact the Ceph documention [specifically indicates](http://docs.ceph.com/docs/master/radosgw/s3/commons/#bucket-and-host-name) a preference for "path-style" bucket specification.