Bug#781767: Makes it unusable for my buckets too
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 debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 is only with buckets with dots in their name, IIUC. This might be important enough to consider unusable, but there is subtle difference in theory between not being usable at all and being usable in some cases. Although, in practice, might be totally unusable (don't know how to estimate this and IMHO it is unusable) Thanks a lot, Rodrigo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 rodr...@sdfg.com.ar wrote: 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 is only with buckets with dots in their name, IIUC. This might be important enough to consider unusable, but there is subtle difference in theory between not being usable at all and being usable in some cases. Although, in practice, might be totally unusable (don't know how to estimate this and IMHO it is unusable) Thanks a lot, Rodrigo
Bug#781767: Makes it unusable for my buckets too
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. 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 bucket.with.dot.s3.amazonaws.com DNS names from matching *.s3.amazonaws.com wildcard certificates. But that's exactly what S3 uses. So we had to add a custom certificate checker into v1.5.2 to fix it correctly. We were past freeze for updating packages in jesse at that point, so we couldn't get the fix into the main release. (in Fedora, we can easily issue updates into an updates repo, so I didn't think much about it.; apparently that's harder in Debian to release updates). On Fri, Jun 12, 2015 at 4:05 PM, Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: 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 with release team, we might be able to make 1.5.2 go in jessie p-u (and eventually in the next point release) or drop it from the archive completely. I would have not released jessie with that package if I had been aware of its usefulness. (I would have updated it before if had the need of it, but I just didn't know about its existance before I had used it :) ) cheers! G. Il Venerdì 12 Giugno 2015 19:39, Matt Domsch m...@domsch.com ha scritto: 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 Costamagna costamagnagianfra...@yahoo.it wrote: 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 to be fixed, you are encouraged to download the source and make the patch apply there I fully agree, but I do not have time to look at it right now :( I'll be happy to ask an spu and upload the package if a patch is provided! cheers, G. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 jessie-pu) Matt do you know the python release introducing the problem? [1] https://bugs.debian.org/788607 thanks in advance, Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 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 jessie-pu) Matt do you know the python release introducing the problem? [1] https://bugs.debian.org/788607 thanks in advance, Gianfranco
Bug#781767: Makes it unusable for my buckets too
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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
Bug#781767: Makes it unusable for my buckets too
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 with release team, we might be able to make 1.5.2 go in jessie p-u (and eventually in the next point release) or drop it from the archive completely. I would have not released jessie with that package if I had been aware of its usefulness. (I would have updated it before if had the need of it, but I just didn't know about its existance before I had used it :) ) cheers! G. Il Venerdì 12 Giugno 2015 19:39, Matt Domsch m...@domsch.com ha scritto: 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 Costamagna costamagnagianfra...@yahoo.it wrote: 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 to be fixed, you are encouraged to download the source and make the patch apply there I fully agree, but I do not have time to look at it right now :( I'll be happy to ask an spu and upload the package if a patch is provided! cheers, G. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 bucket.with.dot.s3.amazonaws.com DNS names from matching *.s3.amazonaws.com wildcard certificates. But that's exactly what S3 uses. So we had to add a custom certificate checker into v1.5.2 to fix it correctly. We were past freeze for updating packages in jesse at that point, so we couldn't get the fix into the main release. (in Fedora, we can easily issue updates into an updates repo, so I didn't think much about it.; apparently that's harder in Debian to release updates). On Fri, Jun 12, 2015 at 4:05 PM, Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: 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 with release team, we might be able to make 1.5.2 go in jessie p-u (and eventually in the next point release) or drop it from the archive completely. I would have not released jessie with that package if I had been aware of its usefulness. (I would have updated it before if had the need of it, but I just didn't know about its existance before I had used it :) ) cheers! G. Il Venerdì 12 Giugno 2015 19:39, Matt Domsch m...@domsch.com ha scritto: 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 Costamagna costamagnagianfra...@yahoo.it wrote: 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 to be fixed, you are encouraged to download the source and make the patch apply there I fully agree, but I do not have time to look at it right now :( I'll be happy to ask an spu and upload the package if a patch is provided! cheers, G.
Bug#781767: Makes it unusable for my buckets too
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 be processed in a week or two. what is the problem on enabling official backports? http://backports.debian.org/Instructions/ :) cheers, G. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 2) change the upstream commit to apply on top of 1.5.0~rc1 version 3) backport the 1.5.2 to jessie-backports. 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 :) Thanks a lot, Rodrigo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 days (a wrong link) the backport is already on the queue delayed/6 and will be processed in a week or two. what is the problem on enabling official backports? http://backports.debian.org/Instructions/ Not any particular problem, just that the jessie version seems totally useless... Like, using the backport because jessie is buggy and not because I **need** a newer version is not common, IMHO. Also, the backport will probably be updated and change the version in the future and a regular jessie package would not. So, maybe there are backwards incompatible changes or something... These are the disadvantages besides having, IMHO, a broken package in jessie. Thanks a lot, Rodrigo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 to be fixed, you are encouraged to download the source and make the patch apply there I fully agree, but I do not have time to look at it right now :( I'll be happy to ask an spu and upload the package if a patch is provided! cheers, G. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 Costamagna costamagnagianfra...@yahoo.it wrote: 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 to be fixed, you are encouraged to download the source and make the patch apply there I fully agree, but I do not have time to look at it right now :( I'll be happy to ask an spu and upload the package if a patch is provided! cheers, G.
Bug#781767: Makes it unusable for my buckets too
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
Bug#781767: Makes it unusable for my buckets too
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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 from testing fixes it too. If I can help with testing or something, please let me know Thanks a lot, Rodrigo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781767: Makes it unusable for my buckets too
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 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 from testing fixes it too. If I can help with testing or something, please let me know Thanks a lot, Rodrigo
Bug#781767: Makes it unusable for my buckets too
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 usr@cotton:~$ s3cmd ls s3://bucket.with.dots WARNING: Retrying failed request: /?delimiter=/ (hostname 'bucket.with.dots.s3.amazonaws.com' doesn't match either of '*.s3.amazonaws.com', 's3.amazonaws.com') WARNING: Waiting 3 sec... ^CSee ya! usr@cotton:~$ s3cmd --debug ls s3://bucket.with.dots DEBUG: ConfigParser: Reading file '/home/usr/.s3cfg' DEBUG: ConfigParser: access_key-AK...17_chars...Q DEBUG: ConfigParser: bucket_location-US DEBUG: ConfigParser: cloudfront_host-cloudfront.amazonaws.com DEBUG: ConfigParser: default_mime_type-binary/octet-stream DEBUG: ConfigParser: delete_removed-False DEBUG: ConfigParser: dry_run-False DEBUG: ConfigParser: enable_multipart-True DEBUG: ConfigParser: encoding-UTF-8 DEBUG: ConfigParser: encrypt-False DEBUG: ConfigParser: follow_symlinks-False DEBUG: ConfigParser: force-False DEBUG: ConfigParser: get_continue-False DEBUG: ConfigParser: gpg_command-/usr/bin/gpg DEBUG: ConfigParser: gpg_decrypt-%(gpg_command)s -d --verbose --no-use-agent --batch --yes --passphrase-fd %(passphrase_fd)s -o %(output_file)s %(input_file)s DEBUG: ConfigParser: gpg_encrypt-%(gpg_command)s -c --verbose --no-use-agent --batch --yes --passphrase-fd %(passphrase_fd)s -o %(output_file)s %(input_file)s DEBUG: ConfigParser: gpg_passphrase-ph...18_chars...d DEBUG: ConfigParser: guess_mime_type-True DEBUG: ConfigParser: host_base-s3.amazonaws.com DEBUG: ConfigParser: host_bucket-%(bucket)s.s3.amazonaws.com DEBUG: ConfigParser: human_readable_sizes-False DEBUG: ConfigParser: invalidate_on_cf-False DEBUG: ConfigParser: list_md5-False DEBUG: ConfigParser: log_target_prefix- DEBUG: ConfigParser: mime_type- DEBUG: ConfigParser: multipart_chunk_size_mb-15 DEBUG: ConfigParser: preserve_attrs-True DEBUG: ConfigParser: progress_meter-True DEBUG: ConfigParser: proxy_host- DEBUG: ConfigParser: proxy_port-0 DEBUG: ConfigParser: recursive-False DEBUG: ConfigParser: recv_chunk-4096 DEBUG: ConfigParser: reduced_redundancy-False DEBUG: ConfigParser: secret_key-YM...37_chars...k DEBUG: ConfigParser: send_chunk-4096 DEBUG: ConfigParser: simpledb_host-sdb.amazonaws.com DEBUG: ConfigParser: skip_existing-False DEBUG: ConfigParser: socket_timeout-300 DEBUG: ConfigParser: urlencoding_mode-normal DEBUG: ConfigParser: use_https-True DEBUG: ConfigParser: verbosity-WARNING DEBUG: ConfigParser: website_endpoint-http://%(bucket)s.s3-website-%(location)s.amazonaws.com/ DEBUG: ConfigParser: website_error- DEBUG: ConfigParser: website_index-index.html DEBUG: Updating Config.Config cache_file - DEBUG: Updating Config.Config encoding - UTF-8 DEBUG: Updating Config.Config follow_symlinks - False DEBUG: Updating Config.Config verbosity - 10 DEBUG: Unicodising 'ls' using UTF-8 DEBUG: Unicodising 's3://bucket.with.dots' using UTF-8 DEBUG: Command: ls DEBUG: Bucket 's3://bucket.with.dots': DEBUG: SignHeaders: 'GET\n\n\n\nx-amz-date:Thu, 11 Jun 2015 19:27:16 +\n/bucket.with.dots/' DEBUG: CreateRequest: resource[uri]=/ DEBUG: SignHeaders: 'GET\n\n\n\nx-amz-date:Thu, 11 Jun 2015 19:27:16 +\n/bucket.with.dots/' DEBUG: Processing request, please wait... DEBUG: get_hostname(bucket.with.dots): bucket.with.dots.s3.amazonaws.com DEBUG: ConnMan.get(): creating new connection: https://bucket.with.dots.s3.amazonaws.com WARNING: Retrying failed request: /?delimiter=/ (hostname 'bucket.with.dots.s3.amazonaws.com' doesn't match either of '*.s3.amazonaws.com', 's3.amazonaws.com') WARNING: Waiting 3 sec... DEBUG: SignHeaders: 'GET\n\n\n\nx-amz-date:Thu, 11 Jun 2015 19:27:19 +\n/bucket.with.dots/' DEBUG: Processing request, please wait... DEBUG: get_hostname(bucket.with.dots): bucket.with.dots.s3.amazonaws.com DEBUG: ConnMan.get(): creating new connection: https://bucket.with.dots.s3.amazonaws.com WARNING: Retrying failed request: /?delimiter=/ (hostname 'bucket.with.dots.s3.amazonaws.com' doesn't match either of '*.s3.amazonaws.com', 's3.amazonaws.com') WARNING: Waiting 6 sec... ^CSee ya!
