http://bugzilla.suse.com/show_bug.cgi?id=1095041 http://bugzilla.suse.com/show_bug.cgi?id=1095041#c14 --- Comment #14 from Martin Wilck <martin.wilck@suse.com> ---
yeah, saw that already. Seriously: We are entering a dependency circle here. The problem described in this bug isn't relevant for SLE-12 and Leap 42, as we still ship python-requests 2.11 there. This is still true for SLE-12-SP4, AFAICS. So, at least as far as this problem here is concerned, we can stay with botocore 1.10 just fine in SLE-12 and Leap 42. OTOH, in factory, SLE15, and Leap15, we have the need to update botocore because it just doesn't work at all with the shipped python-requests (2.19 / 2.18, respectively). So from my point of view it'd make an awful lot of sense to accept botocore 1.11 into factory and SLE15, while going with 1.10 for SLE12. I'm having a bit of a hard time trying to understand why SLE12 needs to get this cutting-edge update at all. Stuff like this ought to go to 15 in my understanding. -- You are receiving this mail because: You are on the CC list for the bug.