Your message dated Sun, 25 Aug 2019 21:21:36 +0200 with message-id <2e905e6b-633b-d7b4-9ec1-db8c85d2dee8@debian.org> and subject line Re: Bug#932101: release-notes: S3QL unable to resolve hostname due to S3 URL format change has caused the Debian Bug report #932101, regarding release-notes: S3QL unable to resolve hostname due to S3 URL format change to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 932101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932101 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: release-notes: S3QL unable to resolve hostname due to S3 URL format change
- From: Shannon Dealy <dealy@deatech.com>
- Date: Sun, 14 Jul 2019 19:24:34 -0700
- Message-id: <156315747484.12179.14478765489512155563.reportbug@zaphod.deatech.com>
Package: release-notes Severity: normal Dear Maintainer, After upgrading from Stretch to Buster, I was unable to use S3QL with any of my Amazon S3 buckets. All attempts to access gave errors like: ERROR: Can't connect to backend: unable to resolve hostname I was eventually able to track the problem down to a change in the format of the Amazon S3 URL which occurred two years ago. The new format of the URL is: s3://<region>/<bucket>/<prefix> Note the addition of a "region" section in the URL. Unfortunately this change is not displayed by "apt-listchanges" during the upgrade, nor is it documented in the release notes. Please add this information to the release notes for Buster so that others don't waste hours trying to figure it out. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (990, 'stable'), (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
- To: 932101-done@bugs.debian.org
- Subject: Re: Bug#932101: release-notes: S3QL unable to resolve hostname due to S3 URL format change
- From: Paul Gevers <elbrus@debian.org>
- Date: Sun, 25 Aug 2019 21:21:36 +0200
- Message-id: <2e905e6b-633b-d7b4-9ec1-db8c85d2dee8@debian.org>
- In-reply-to: <895bdb43-3ddc-506d-0a2a-91a1e5956f70@debian.org>
- References: <156315747484.12179.14478765489512155563.reportbug@zaphod.deatech.com> <895bdb43-3ddc-506d-0a2a-91a1e5956f70@debian.org>
Hi, On 19-07-2019 21:57, Paul Gevers wrote: > So, something along the following lines should work? > > <section id="s3ql"> > <!-- stretch to buster --> > <title> > S3QL URL changes for Amazon S3 buckets > </title> > <para> > When using <systemitem role="package">s3ql</systemitem> with > Amazon S3 buckets, the configuration needs updating for a change > in the URL. The new format is: > > <programlisting>s3://<region>/<bucket>/<prefix></programlisting> > </para> > </section> Committed. PaulAttachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---