My preference is the backport of 1.5.2. That picks up signature v4 support which allows Frankfurt and China regions too. On Jun 12, 2015 4:02 AM, "Gianfranco Costamagna" < costamagnagianfra...@yahoo.it> wrote:
> Hi Rodrigo and Matt, > > I tried to apply the upstream commit to 1.5.0~rc1-2 and it doesn't apply > cleanly. > > I see two/three possible solutions: > 1) upgrade to stretch (just almost jocking) or apt-pinning s3cmd from there > 2) change the upstream commit to apply on top of 1.5.0~rc1 version > 3) backport the 1.5.2 to jessie-backports. > > > It is up to you, > Rodrigo you can do 1, Matt you can do 2, and I can do 3. > > I would prefer a stable-release-update, but backporting the new 1.5.2, > might be better because some new features have been added > > In the meanwhile you have your backport ready there > > http://debomatic-amd64.debian.net/distribution#jessie-backports/s3cmd/1.5.2-2~bpo8+1/buildlog > :) > > cheers, > > G. > > > > > > Il Venerdì 12 Giugno 2015 1:36, Rodrigo Campos <rodr...@sdfg.com.ar> ha > scritto: > On Thu, Jun 11, 2015 at 04:42:15PM -0500, Matt Domsch wrote: > > The copy in jesse's repository is 1.5.0~rc1-2 which is not v1.5.2 where > the fix > > was committed. I see the same failure if I simply apt-get install s3cmd > on a > > new jesse install. v1.5.2 is in experimental and unstable or can be > downloaded > > from https://github.com/s3tools/s3cmd. > > Exactly. And my point is to fix this in jessie, if possible. > > As I said in my first mail, it renders the package unusable to me (and all > people who is using dots in the buckets name). I upgraded to jessie and > because > of this bug some scripts are now broken. > > > > > > > Thanks a lot, > Rodrigo > >
