On Tue, Jun 16, 2015 at 10:12:03AM -0500, Matt Domsch wrote:
Buckets with dots is the AWS recommended method, and is required for all
regions except for us-east-1. It becomes usable if you use
Ohh, didn't know that. Then I fully agree =)
Thanks a lot,
Rodrigo
--
To UNSUBSCRIBE, email to
On Sat, Jun 13, 2015 at 07:24:15AM +, Gianfranco Costamagna wrote:
Control: severity -1 grave
Control: found -1 1.5.0~rc1-2
Control: fixed -1 1.5.2-1
thanks
I'm setting the correct severity, since the jessie package is completely
unusable.
Well, it's not completely unusable. It
Buckets with dots is the AWS recommended method, and is required for all
regions except for us-east-1. It becomes usable if you use
--no-check-certificate or --no-ssl but that's bad practice too. So in
practice it is essentially unusable.
On Tue, Jun 16, 2015 at 9:55 AM, Rodrigo Campos
Control: severity -1 grave
Control: found -1 1.5.0~rc1-2
Control: fixed -1 1.5.2-1
thanks
I'm setting the correct severity, since the jessie package is completely
unusable.
Il Venerdì 12 Giugno 2015 23:39, Matt Domsch m...@domsch.com ha scritto:
The breakage predates you Gianfranco.
Hi all,
I opened a jessie-p-u request here [1]
I tried to explain (sum this conversation) in the best way I could, please read
and correct if I wrote anything wrong there.
Maybe something about this can be fixed with a python upload?
(just wondering how bad might be reverting the check in a
Python upstream included the ssl cert checks. Jessie picked up the new
python upstream release. That is all well and good. The right thing to do
is to get s3cmd updated.
On Jun 13, 2015 3:21 AM, Gianfranco Costamagna
costamagnagianfra...@yahoo.it wrote:
Hi all,
I opened a jessie-p-u request
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
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
Hi Matt,
what do you mean by broke s3cmd? you mean the current jessie version is
completely unusable?
I honestly never tried it, my first release (used and packaged) as you know has
been 1.5.2, and I'm using it since some months :)
If the jessie version is completely broken I need to talk
The breakage predates you Gianfranco. Not your fault. Python got updated
in Jesse right before it released. That python added in https ssl
certificate checking for all HTTPSConnection() usage, per the RFC regarding
how to check the certificate. The RFC explicitly disallows
Hi Rodrigo
I'm not doing any of those. I'm just using a python virtualenv right now, but
would love to switch to jessie and avoid it :)
I uploaded a new s3cmd on unstable, that will hopefully migrate to testing in 5
days (a wrong link)
the backport is already on the queue delayed/6
and will
On Fri, Jun 12, 2015 at 08:57:02AM +, Gianfranco Costamagna 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
On Fri, Jun 12, 2015 at 03:25:52PM +, Gianfranco Costamagna wrote:
Hi Rodrigo
I'm not doing any of those. I'm just using a python virtualenv right now, but
would love to switch to jessie and avoid it :)
I uploaded a new s3cmd on unstable, that will hopefully migrate to testing in
5
Control: tags -1 -patch
thanks
Not any particular problem, just that the jessie version seems totally
useless...
not for me :)
this bug affects only part of people, not all of them ;)
Anyway, the backport is still useful for people who want to try new features,
and
if you really want jessie
By the time we knew Jesse's python SSL library change (actual cert
validation) broke s3cmd it was too late to update the s3cmd package to a
new enough version to fix it. And no I have not done a 1.5.0~rc1-X that is
really just 1.5.2. But that is what is needed.
On Jun 12, 2015 10:55 AM, Gianfranco
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,
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
Hi,
Any news on this ? I've upgraded to jessie and scripts using s3cmd broke because
of this bug. It renders the package unusable to me (and all using dots in the
buckets name).
As a workaround, just in case, I've used s3cmd from a python virtual env using
the last release. Probably the package
Please run a failing case with --debug and report results. v1.5.2 should
not fail on Debian any longer.
On Thu, Jun 11, 2015 at 1:08 PM, Rodrigo Campos rodr...@sdfg.com.ar wrote:
Hi,
Any news on this ? I've upgraded to jessie and scripts using s3cmd broke
because
of this bug. It renders
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
20 matches
Mail list logo
