SRU: bump version to make compatible with upstream awscli requirements

[Cody Shepherd]

Pull in upstream [1] changes to bump this package version to the latest release version (0.3.3) as required by upstream awscli [2].

[Impact]

 * This bug is intended to work in tandem with bugs for awscli [3] and python-botocore [4] to update these packages to include modern features and enable the use of awscli in cloud images.

 * bumping the version of this package will meet requirements set by upstream awscli, as well as the SRU-updated awscli debian package.

[Test Case]

 * install python3-s3transfer using apt

 * run `dpkg-query -s python3-s3transfer`, verify installed version is 0.3.3

[Regression Potential]

 * The biggest risks would be causing regression in awscli, which depends on this package

 * other regression potential would be that the package breaks for current default python versions in supported Ubuntu releases

[Other Info]

 * Nothing at this time

[1] https://github.com/boto/s3transfer
[2] https://github.com/aws/aws-cli/blob/3866d9c7d116d6e7ced23c2426720782af0177bf/setup.cfg#L10
[3] https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1867673
[4] https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485

[Brian Murray (brian-murray)]

Hello Cody, or anyone else affected,

Accepted python-s3transfer into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python-s3transfer/0.3.3-1ubuntu0.19.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Brian Murray (brian-murray)]

Hello Cody, or anyone else affected,

Accepted python-s3transfer into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python-s3transfer/0.3.3-1ubuntu0.18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Brian Murray (brian-murray)]

Hello Cody, or anyone else affected,

Accepted python-s3transfer into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python-s3transfer/0.3.3-1ubuntu0.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[David Krauser (davidkrauser)]

Performed verification steps on a fresh bionic VM:

- Enable proposed
- apt install python-s3transfer/bionic-proposed and python3-s3transfer/bionic-proposed
- dpkg -s python-s3transfer shows v0.3.3
- dpkg -s python3-s3transfer shows v0.3.3

[David Krauser (davidkrauser)]

Performed verification steps on a fresh xenial VM:

- Enable proposed
- apt install python-s3transfer/xenial-proposed and python3-s3transfer/xenial-proposed
- dpkg -s python-s3transfer shows v0.3.3
- dpkg -s python3-s3transfer shows v0.3.3

[David Krauser (davidkrauser)]

Performed verification steps on a fresh eoan VM:

- Enable proposed
- apt install python-s3transfer/eoan-proposed and python3-s3transfer/eoan-proposed
- dpkg -s python-s3transfer shows v0.3.3
- dpkg -s python3-s3transfer shows v0.3.3

[David Krauser (davidkrauser)]

The python-boto3 unit and functional tests seem to do a pretty good job exercising python-botocore and python-s3transfer. I ran those tests against botocore/updates and s3transfer/updates for each suite, and compared those results to the same tests run against botocore/proposed and s3transfer/proposed for each suite. The raw results are available here, alongside the script used to run the tests:

https://git.launchpad.net/~davidkrauser/+git/logs/tree/LP1875485/20200714?id=17b08c1f3ea389dd3f49f2a511f6ed6ed45c6ac4

The summary is as follows:

==> bionic-proposed-py.log <==
OK (SKIP=1)

==> bionic-proposed-py3.log <==
OK

==> bionic-updates-py.log <==
OK (SKIP=1)

==> bionic-updates-py3.log <==
OK

==> eoan-proposed-py.log <==
OK (SKIP=1)

==> eoan-proposed-py3.log <==
OK

==> eoan-updates-py.log <==
OK (SKIP=1)

==> eoan-updates-py3.log <==
OK

==> xenial-proposed-py.log <==
FAILED (SKIP=1, errors=10, failures=1)

==> xenial-proposed-py3.log <==
FAILED (errors=10, failures=1)

==> xenial-updates-py.log <==
FAILED (SKIP=1, errors=1, failures=1)

==> xenial-updates-py3.log <==
FAILED (errors=1, failures=1)

Seeing that the awscli verification for xenial against this package failed, and the test results are worse here against proposed for xenial, I'm marking this as failed verification for xenial. The other suites look to be in good order.

Also: the documentation related python-boto3 tests were skipped for these runs. I couldn't get them to pass reliably, even with the dependencies from updates.

[Launchpad Janitor (janitor)]

This bug was fixed in the package python-s3transfer - 0.3.3-1ubuntu0.19.10.1

---------------
python-s3transfer (0.3.3-1ubuntu0.19.10.1) eoan; urgency=medium

  * SRU the latest package version to 19.10 (LP: #1880999).
  * debian/control: re-add the python-s3transfer py2 package.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 17 Jun 2020 11:26:48 +0200

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for python-s3transfer has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package python-s3transfer - 0.3.3-1ubuntu0.18.04.1

---------------
python-s3transfer (0.3.3-1ubuntu0.18.04.1) bionic; urgency=medium

  * SRU the latest package version to 18.04 (LP: #1880999).
  * debian/control: re-add the python-s3transfer py2 package.
  * debian/control: adjust debhelper requirements.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 17 Jun 2020 11:26:48 +0200

[Lukas Märdian (slyon)]

Hi Brian,

I performed the verification steps on a fresh xenial LXC (using python-botocore 1.16.19+repack-1ubuntu0.16.04.2 from LP: #1875485):

- Enable proposed
- apt install python-s3transfer/xenial-proposed and python3-s3transfer/xenial-proposed
- dpkg -s python-s3transfer shows v0.3.3
- dpkg -s python3-s3transfer shows v0.3.3

root@namely-premium-longhorn:~# dpkg -l | grep s3transfer
ii python-s3transfer 0.3.3-1ubuntu0.16.04.1 all Amazon S3 Transfer Manager for Python2
ii python3-s3transfer 0.3.3-1ubuntu0.16.04.1 all Amazon S3 Transfer Manager for Python3

Additionally, I executed David's test script, to run the python-boto3 unit and functional tests exercising python-botocore and python-s3transfer. I ran those tests against botocore/updates and s3transfer/updates for xenial, and compared those results to the same tests run against botocore/proposed and s3transfer/proposed for xenial. The failures observed in -proposed are equal to the baseline (-updates) failures. The errors observed in David's previous test runs on xenial are gone with 1.16.19+repack-1ubuntu0.16.04.2.

The raw results are available here, alongside the (modified) script used to run the tests:
https://git.launchpad.net/~slyon/+git/files/tree/LP1875485

==> xenial-proposed-py.log <==
test_serialize_bytes (tests.unit.dynamodb.test_types.TestSerializer) ... SKIP
ERROR: test_resource_lazy_loads_properties
FAIL: tests.functional.test_smoke.test_api_versions_synced_with_botocore
FAILED (SKIP=1, errors=1, failures=1)

==> xenial-proposed-py3.log <==
ERROR: test_resource_lazy_loads_properties
FAIL: tests.functional.test_smoke.test_api_versions_synced_with_botocore
FAILED (errors=1, failures=1)

==> xenial-updates-py.log <==
test_serialize_bytes (tests.unit.dynamodb.test_types.TestSerializer) ... SKIP
ERROR: test_resource_lazy_loads_properties
FAIL: tests.functional.test_smoke.test_api_versions_synced_with_botocore
FAILED (SKIP=1, errors=1, failures=1)

==> xenial-updates-py3.log <==
ERROR: test_resource_lazy_loads_properties
FAIL: tests.functional.test_smoke.test_api_versions_synced_with_botocore
FAILED (errors=1, failures=1)

[Launchpad Janitor (janitor)]

This bug was fixed in the package python-s3transfer - 0.3.3-1ubuntu0.16.04.1

---------------
python-s3transfer (0.3.3-1ubuntu0.16.04.1) xenial; urgency=medium

  * SRU the latest package version to 16.04 (LP: #1880999).
  * debian/control: re-add the python-s3transfer py2 package.
  * debian/control: adjust debhelper requirements.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 17 Jun 2020 11:26:48 +0200

[Jochen Sprickerhof (v-launchpad-jochen-sprickerhof-de)]

You probably wanted 0.3.3-1~ubuntu0.18.04.1 as the version here because now the version in bionic-updates is higher then the on in focal (same for xenial):

https://packages.ubuntu.com/search?suite=all&searchon=names&keywords=python3-s3transfer

[Lukas Märdian (slyon)]

You are right. I prepared a small fix for that, which should also be SRU'ed into Focal & Groovy.