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.
On Thu, Jun 11, 2015 at 2:30 PM, Rodrigo Campos <rodr...@sdfg.com.ar> wrote: > On Thu, Jun 11, 2015 at 01:38:01PM -0500, Matt Domsch wrote: > > Please run a failing case with --debug and report results. > > I'm not sure why you need this, as it's trivial to reproduce and the > original > report says which commit should fix it. But here it goes anyways... > > > v1.5.2 should not > > fail on Debian any longer. > > But that is not on jessie :) > > > > > Thanks a lot, > Rodrigo >
