In our development environment, we utilize both pinned and unpinned package versions.

On July 17, 2024, a new version of setuptools (71.0.0) was released, which has introduced compatibility issues with some older libraries. This likely explains the current errors, as our CI system has recently rebuilt its image for testing and is now encountering failures.

In the wazo-lib-rest-client, the stevedore package has been pinned to version 3.2.2 (Bullseye version), but the setuptools package has not been pinned.

They are now, incompatible, so we have these following options

1. Pin setuptools==52.0.0

   • pro: easy, use same logic than stevedore/requests, test same version than prod

   • con: pinning setuptools can be a painful on other packages and may require us to keep old packages not pinned (test-requirements.txt)

2. Remove stevedore pinning

   • pro: easy

   • con: don’t test production version anymore

3. Backport stevedore from bookworm (4.0.2)

   • pro: going forward with bookworm, compatible with latest setuptools, still tests production version

   • con: take more time to do (+1-2 hours)

4. Pin setuptools on CI and say to dev to use <71

   • pro: quick

   • con: painful for dev to remember to use specific version

Order of preference: 3-1-2

fblackburn will try to implement solution 3 and fallback on another solution if it’s not worth it