diff options
| author | Maximilian Bosch <maximilian@mbosch.me> | 2024-01-20 15:10:49 +0100 |
|---|---|---|
| committer | Maximilian Bosch <maximilian@mbosch.me> | 2024-01-20 15:13:09 +0100 |
| commit | c913a0bc0da401762630277afe845ff2cf8289a3 (patch) | |
| tree | a275388150143558696c36d8d95a4934415e2479 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | d0d38247f01c2d0d6f4d8ab46401ead9a658de37 (diff) | |
python3.pkgs.opentelemetry-instrumentation: 1.16.0 -> 0.43b0
This may seem like a downgrade, but actually it isn't:
the library tags releases as 0.Xb0 with the title "1.22.0 / 0.43b0".
Until 1.16 two tags were pushed, for 1.16 and 0.X. This isn't the case
anymore, so 0.43b0 is far newer than 1.16. This has practical
implications already since `opentelemetry-instrumentation-wsgi` doesn't
build at all:
Checking runtime dependencies for opentelemetry_instrumentation_wsgi-0.37b0-py3-none-any.whl
- opentelemetry-semantic-conventions==0.37b0 not satisfied by version 0.42b0
Originally, this package was published via 0.X, but this was changed
in 74303025237e4df97ba3597b089c1f1c596b9a71 which was a downgrade
already. This looks like a bug in the automatic python updater and
should be be skipped (or 1.x releases should be ignored).
ChangeLogs:
* https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.38b0
* https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.39b0
* https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.40b0
* https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.41b0
* https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.42b0
* https://github.com/open-telemetry/opentelemetry-python-contrib/releases/tag/v0.43b0
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions