Introduce plusWorkaround: generate copy of file with '+' -> ' ' to workaround S3/apt bug. #98

man/aptly.1.ronn.tmpl

@@ -49,7 +49,8 @@ Configuration file is stored in JSON format (default values shown below):
           "prefix": "",
           "acl": "public-read",
           "storageClass": "",
-          "encryptionMethod": ""
+          "encryptionMethod": "",
+          "plusWorkaround": false
         }
     }
 
@@ -97,7 +98,7 @@ Options:
     specifies paramaters for short PPA url expansion, if left blank they default
     to output of `lsb_release` command
 
-  * `S3PublisEndpoints`:
+  * `S3PublishEndpoints`:
     configuration of Amazon S3 publishing endpoints (see below)
 
 ## S3 PUBLISHING ENDPOINTS
@@ -129,7 +130,14 @@ and associated settings:
    * `encryptionMethod`:
      (optional) server-side encryption method, defaults to none. Currently
      the only available encryption method is `AES256`
-
+   * `plusWorkaround`:
+     (optional) workaround misbehavior in apt and Amazon S3
+     for files with `+` in filename by
+     creating two copies of package files with `+` in filename: one original
+     and another one with spaces instead of plus signs
+     With `plusWorkaround` enabled, package files with plus sign
+     would be stored twice. aptly might not cleanup files with spaces when published
+     repository is dropped or updated (switched) to new version of repository (snapshot).
 
 In order to publish to S3, specify endpoint as `s3:endpoint-name:` before
 publishing prefix on the command line, e.g.: