-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi, since the 1.6.0 version migrated today in testing I uploaded a new
1.6.0 version with the upstream patch on unstable a few seconds ago,
and a backport on delayed/6 queue.
cheers,
Gianfranco
On Fri, 25 Sep 2015 09:21:50 -0500 Matt Domsch wrote
https://github.com/s3tools/s3cmd/issues/636 filed to track in upstream's
tracker.
On Fri, Sep 25, 2015 at 8:09 AM, Conrad Hughes wrote:
> Hi Gianfranco,
>
> Thanks again for such a rapid turnaround! So 1.6.0-1 returns to the
> behaviour of 1.5.0~rc1-2: it can run the whole sync despite the 403
Hi Gianfranco,
Thanks again for such a rapid turnaround! So 1.6.0-1 returns to the
behaviour of 1.5.0~rc1-2: it can run the whole sync despite the 403
errors, but it still leaves an empty temporary file for every failure..
Regards,
Conrad
Hi Gianfranco,
Thanks for the fast response.
> can you please try 1.5.2 from Stretch?
I tried 1.5.2-3~bpo8+1 from jessie-backports; hope that's good enough.
It's a substantial regression: not only does it still leave empty temp
files, but it terminates on the first permission error, so I can no
Well, while we are waiting for an official answer from upstream,
I just uploaded on debian/unstable the new 1.6.0 version, I would appreciate
some testing here :)
You can grab the deb files as soon as they are built from here [1] or wait for
dinstall and grab from unstable.
[1] http://incomin
Hi Conrad, can you please try 1.5.2 from Stretch?
thanks
G.
Il Venerdì 25 Settembre 2015 13:27, Conrad J.C. Hughes (for Debian package
stuff) ha scritto:
Package: s3cmd
Version: 1.5.0~rc1-2
Severity: normal
Tags: upstream
Dear Maintainer,
On receipt of a permission error during s3cmd sync
Package: s3cmd
Version: 1.5.0~rc1-2
Severity: normal
Tags: upstream
Dear Maintainer,
On receipt of a permission error during s3cmd sync, a local empty temporary
file is
left. Would be nice if it was deleted.
The particular remote error I'm getting is this one:
WARNING: Remote file S3Error:
7 matches
Mail list logo