Bug#932101: release-notes: S3QL unable to resolve hostname due to S3 URL format change

[Shannon Dealy <dealy@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