Ansible's dependencies' depencies: python-responses and urllib3 < 2
Hi Matej, hi all, I am almost done with getting Ansible and its tools packaged for SLES15 with the new python3.11 macro. The only thing I had to do was patch python-responses to not require urllib3 > 2, as botocore and python-elastic* still require 1.x (which is unlikely to change in the near future, according to the upstream discussions). I basically just removed the constraint, but kept all of the patches (without digging deeper). And everything seemed to build (I have not yet tested the packages).
I would like to get your opinion. Does python-response (after Matej's patches) really require 2.x of urllib3? Or does it still work with 1.x? What would be the best way to solve this? Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Am 09.05.23 um 12:48 schrieb Johannes Kastl:
Hi Matej, hi all,
I am almost done with getting Ansible and its tools packaged for SLES15 with the new python3.11 macro.
The only thing I had to do was patch python-responses to not require urllib3 > 2, as botocore and python-elastic* still require 1.x (which is unlikely to change in the near future, according to the upstream discussions).
FTR: https://github.com/boto/botocore/issues/2926
[snip] What would be the best way to solve this?
IMHO revert to urllib3 < 2 until more packages catch up with it. Your project isn't the only one suffering from it, whole Tumbleweed is. (See Staging:N and that is only the lettered staging for Ring1).
Kind Regards, Johannes
- Ben
Hi Ben, On 09.05.23 at 21:42 Ben Greiner wrote:
Am 09.05.23 um 12:48 schrieb Johannes Kastl:
I am almost done with getting Ansible and its tools packaged for SLES15 with the new python3.11 macro.
The only thing I had to do was patch python-responses to not require urllib3 > 2, as botocore and python-elastic* still require 1.x (which is unlikely to change in the near future, according to the upstream discussions).
Yes. And:
https://github.com/elastic/elastic-transport-python/issues/102
[snip] What would be the best way to solve this?
IMHO revert to urllib3 < 2 until more packages catch up with it. Your project isn't the only one suffering from it, whole Tumbleweed is. (See Staging:N and that is only the lettered staging for Ring1).
That indeed sounds like a good plan. Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
participants (2)
-
Ben Greiner -
Johannes Kastl