Great, let's continue the discussion at https://github.com/jclouds/jclouds/pull/1267 .
jclouds commits must merge to master first although I can backport them to 2.1.x. Timing releases is a sore point but S3Proxy already upgraded to 2.1.2-SNAPSHOT so S3Proxy's snapshot releases and Docker images will immediately include such fixes. Unfortunately its next release will now be gated on jclouds. On Tue, Jan 15, 2019 at 10:20:45AM -0500, Justinus Menzel wrote: > Andrew, thank you for responding. > I really need both parts. Hence I made changes to s3proxy which rely on > changes to jclouds. > I can setup the pull request with target https://github.com/gaul/s3proxy > But it also needs the jclouds change where jclouds back-end issues the > 'list-type=2' request. > I'll try to setup a pull request into the jclouds repo. > Not sure how easily this PR will get accepted and merged. Apparently > changes need to go into master. > How long before master becomes stable and can be used for building/ > releasing s3proxy? > Anyways, I'll give it a shot. > Best, -- Andrew Gaul http://gaul.org/
