You are right. I prepared a small fix for that, which should also be
SRU'ed into Focal & Groovy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880999
Title:
SRU: bump version to make compatible
** Patch added: "fix-version.debdiff"
https://bugs.launchpad.net/ubuntu/eoan/+source/python-s3transfer/+bug/1880999/+attachment/5429488/+files/fix-version.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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=names=python3-s3transfer
--
You received this bug notification because you are a member of
** Tags added: id-5eea51b0f3f7f2772ffde077
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880999
Title:
SRU: bump version to make compatible with upstream awscli requirements
To manage
** Changed in: python-s3transfer (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880999
Title:
SRU: bump version to make compatible with upstream awscli
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.
*
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
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.
*
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
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880999
Title:
SRU: bump version to make compatible with upstream awscli requirements
To manage notifications
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
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
** Tags removed: verification-needed-eoan
** Tags added:
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
** Tags removed: verification-needed-xenial
** Tags
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
** Tags removed: verification-needed-bionic
** Tags
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
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
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
** Changed in: python-s3transfer (Ubuntu)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880999
Title:
SRU: bump version to make compatible
** Tags added: id-5ea6eb3d73f4d32753382fc6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880999
Title:
SRU: bump version to make compatible with upstream awscli requirements
To manage
** Also affects: python-s3transfer (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: python-s3transfer (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: python-s3transfer (Ubuntu Focal)
Importance: Undecided
Status: New
** Also
** Description changed:
- Placeholder: will update with SRU template
+ 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
+
21 matches
Mail list logo
