[SRU] python-botocore out of date
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-botocore (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* the python-botocore package is out of date, and out of sync with python3-botocore in debian [1], for all pockets except groovy-proposed.
* The various outdated versions in, e.g. xenial and bionic, leave out lots of useful botocore functionality.
* SRUing the current version back through supported suites will normalize sdk functionality across supported ubuntu releases.
[Test Case]
* On a machine running xenial, bionic, eoan, or focal:
`apt install python-botocore`
`dpkg -s python-botocore`
verify the package is installed, at its version matches the latest upstream release version, 1.15.46.
[Regression Potential]
* apt-cache rdepends python-botocore reveals no dependent packages, so that should not be an issue.
* however, the awscli tool source does require this package; there are probable configurations in use (e.g. pip install of awscli which use the local version of this package) wherein updates to this package will break users' expectations, especially where the version of botocore is pinned.
* Any users on releases who are pinned to, or otherwise dependent on old versions of python-botocore being in the archive will likely be broken at some point by the package being updated in the archive.
* New bugs introduced by botocore version releases will exist in the updated package
[Other Info]
* The Hardware Enablement exception likely applies here, as updating this package version will enable using functionality of the AWS cloud which are impossible to use with the versions of the cli currently in the archive.
description: | updated |
tags: | added: id-5ea6eb3d73f4d32753382fc6 |
description: | updated |
description: | updated |
tags: | added: id-5eea51b0f3f7f2772ffde077 |
I will sponsor the backports in a moment as these updates do make sense. That being said, the python-botocore binary packages do seem to have a few reverse- dependencies from what I see, so we'd have to make sure we didn't regress those as well:
$ reverse-depends src:python-botocore
Reverse-Recommends
* python3-mapproxy (for python3-botocore)
* snakemake (for python3-botocore)
Reverse-Depends
* awscli (for python3-botocore)
* python3-boto3 (for python3-botocore)
* python3-s3transfer (for python3-botocore)
* python3-sahara (for python3-botocore)
$ reverse-depends -b src:python-botocore Build-Depends- Indep
Reverse-
* awscli (for python3-botocore)
* python-scrapy (for python3-botocore)
* sahara (for python3-botocore)
Reverse- Build-Depends
* python-aws-xray-sdk (for python3-botocore)
* snakemake (for python3-botocore)