[opensuse-factory] Leap 42.1 : awc-cli fails to update because python-s3transfer missing
Hi, Some time ago (a month or so), the auto update brought over a recommended update for "aws-cli, botocore". This update keeps failing; when run from the command line, I get: zypper up aws-cli Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides python-s3transfer >= 0.0.1 needed by aws-cli-1.10.38-6.1.noarch Solution 1: do not install aws-cli-1.10.38-6.1.noarch Solution 2: break aws-cli-1.10.38-6.1.noarch by ignoring some of its dependencies Is this something I should report as a bug, and is there a temporary alternative where python-s3transfer can be obtained? Thanks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/08/2016 06:00, Milan Zimmermann wrote:
Hi,
Some time ago (a month or so), the auto update brought over a recommended update for "aws-cli, botocore". This update keeps failing; when run from the command line, I get:
zypper up aws-cli Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: nothing provides python-s3transfer >= 0.0.1 needed by aws-cli-1.10.38-6.1.noarch Solution 1: do not install aws-cli-1.10.38-6.1.noarch Solution 2: break aws-cli-1.10.38-6.1.noarch by ignoring some of its dependencies
Is this something I should report as a bug, and is there a temporary alternative where python-s3transfer can be obtained?
do package search (1) identifies an unstable version for Leap 42.1 (1) https://software.opensuse.org/package/python-s3transfer?search_term=python-s...
Thanks
-- Michel Normand -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 08/10/2016 12:00 AM, Milan Zimmermann wrote:
Hi,
Some time ago (a month or so), the auto update brought over a recommended update for "aws-cli, botocore". This update keeps failing; when run from the command line, I get:
zypper up aws-cli Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: nothing provides python-s3transfer >= 0.0.1 needed by aws-cli-1.10.38-6.1.noarch Solution 1: do not install aws-cli-1.10.38-6.1.noarch Solution 2: break aws-cli-1.10.38-6.1.noarch by ignoring some of its dependencies
Is this something I should report as a bug,
Yes it is a bug, sorry I forgot to submit a request to Factory when I updated aws-cli. Max has submitted the request for python-s3transfer a few hours ago [1] @Max THANKS Later, Robert [1] https://build.opensuse.org/request/show/418166 -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo
On Wed, 2016-08-10 at 07:53 -0400, Robert Schweikert wrote:
On 08/10/2016 12:00 AM, Milan Zimmermann wrote:
Hi,
Some time ago (a month or so), the auto update brought over a recommended update for "aws-cli, botocore". This update keeps failing; when run from the command line, I get:
zypper up aws-cli Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: nothing provides python-s3transfer >= 0.0.1 needed by aws-cli-1.10.38-6.1.noarch Solution 1: do not install aws-cli-1.10.38-6.1.noarch Solution 2: break aws-cli-1.10.38-6.1.noarch by ignoring some of its dependencies
Is this something I should report as a bug,
Yes it is a bug, sorry I forgot to submit a request to Factory when I updated aws-cli. Max has submitted the request for python-s3transfer a few hours ago [1]
To Factory was no problem, as we have bots blocking the package from entering it it would not end up being installable. The submission done by Max is towards 42.2 The OP was talking about 42.1. The problem was introduced with https:// build.opensuse.org/request/show/409007 there. The correct thing to do would be for * @OP to create a bug report about this (and for the next time: don't wait that long when a maintenance update does not work.. this is always worth a bug report) * the aws-cli maintainer to take care of fixing the deps by submitting the needed packages to openSUSE:Leap:42.1:Update * In the longer run: have maintenance run the factory bot to check that updates adhere to at least some minimal things - like being installable. Cheers, Dominique
On 08/10/2016 08:05 AM, Dominique Leuenberger / DimStar wrote:
On Wed, 2016-08-10 at 07:53 -0400, Robert Schweikert wrote:
On 08/10/2016 12:00 AM, Milan Zimmermann wrote:
Hi,
Some time ago (a month or so), the auto update brought over a recommended update for "aws-cli, botocore". This update keeps failing; when run from the command line, I get:
zypper up aws-cli Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: nothing provides python-s3transfer >= 0.0.1 needed by aws-cli-1.10.38-6.1.noarch Solution 1: do not install aws-cli-1.10.38-6.1.noarch Solution 2: break aws-cli-1.10.38-6.1.noarch by ignoring some of its dependencies
Is this something I should report as a bug,
Yes it is a bug, sorry I forgot to submit a request to Factory when I updated aws-cli. Max has submitted the request for python-s3transfer a few hours ago [1]
To Factory was no problem, as we have bots blocking the package from entering it it would not end up being installable.
The submission done by Max is towards 42.2
The OP was talking about 42.1.
Missed that as the thread is on factory ML. Reading the whole subject is certainly helpful ;)
The problem was introduced with https:// build.opensuse.org/request/show/409007 there.
The correct thing to do would be for * @OP to create a bug report about this (and for the next time: don't wait that long when a maintenance update does not work.. this is always worth a bug report) * the aws-cli maintainer to take care of fixing the deps by submitting the needed packages to openSUSE:Leap:42.1:Update
created request id 418300 Well I maintain aws-cli but did not submit it to Leap 42.1. Looks like the SUSE Maintenance team forwards changes for packages that are also in SLES to openSUSE Leap, that's nice. Thus, somehow it needs to figured out to handle dependency changes in the same way. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo
On Wed, 2016-08-10 at 08:32 -0400, Robert Schweikert wrote:
Well I maintain aws-cli but did not submit it to Leap 42.1. Looks like the SUSE Maintenance team forwards changes for packages that are also in SLES to openSUSE Leap, that's nice. Thus, somehow it needs to figured out to handle dependency changes in the same way.
aws-cli in 42.1 (and also 42.2) is marked to be a SLE package - and thus is supposed to inherit fixes that are published for SLE (this is the main idea behind Leap after all) For python-s3transfer the correct thing, in my opinion, would be to have it also follow the SLE version, so rather submit SUSE:SLE- 12:Update/python-s3transfer to openSUSE:Leap:42.1:Update Future updates to SLE should then automatically follow down to Leap too. Cheers, Dominique
On 08/10/2016 08:37 AM, Dominique Leuenberger / DimStar wrote:
On Wed, 2016-08-10 at 08:32 -0400, Robert Schweikert wrote:
Well I maintain aws-cli but did not submit it to Leap 42.1. Looks like the SUSE Maintenance team forwards changes for packages that are also in SLES to openSUSE Leap, that's nice. Thus, somehow it needs to figured out to handle dependency changes in the same way.
aws-cli in 42.1 (and also 42.2) is marked to be a SLE package - and thus is supposed to inherit fixes that are published for SLE (this is the main idea behind Leap after all)
For python-s3transfer the correct thing, in my opinion, would be to have it also follow the SLE version, so rather submit SUSE:SLE- 12:Update/python-s3transfer to openSUSE:Leap:42.1:Update
Fair enough: created request id 418307 -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo
Thanks Robert!
On Wed, Aug 10, 2016 at 6:53 AM, Robert Schweikert
On 08/10/2016 12:00 AM, Milan Zimmermann wrote:
Hi,
Some time ago (a month or so), the auto update brought over a recommended update for "aws-cli, botocore". This update keeps failing; when run from the command line, I get:
zypper up aws-cli Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: nothing provides python-s3transfer >= 0.0.1 needed by aws-cli-1.10.38-6.1.noarch Solution 1: do not install aws-cli-1.10.38-6.1.noarch Solution 2: break aws-cli-1.10.38-6.1.noarch by ignoring some of its dependencies
Is this something I should report as a bug,
Yes it is a bug, sorry I forgot to submit a request to Factory when I updated aws-cli. Max has submitted the request for python-s3transfer a few hours ago [1]
@Max THANKS
Later, Robert
[1] https://build.opensuse.org/request/show/418166
-- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Dominique Leuenberger / DimStar -
Milan Zimmermann -
Normand -
Robert Schweikert