Hi all,

Second try sending this message. There seems to be a bug in aerc when sending a
signed mail which is continued from a draft. I CC'ed all RFS bugs below in my
first attempt.

I'm looking for a sponsor for a set of five related uploads. Together
they update python-mcp to 2.3.0, which is needed by home-assistant.
mcp 2.x pulled in a few new packages and fixes to existing ones. All
packages are team-maintained and live under python-team/packages on
salsa.

I've used a lot of LLM help from inference.debian.net and Claude. Not all
commits are marked with an Assisted-by, but I want to mention it for those who
care. LLM usage allowed me to learn faster, get the structure faster, debug
builds and tests faster. [1]

Reviews and comments are very welcome, and I'm happy to split this up
if that's easier for a sponsor. Let me know if I should bring these up for
sponsorship in a different way.

I kept a lot of documentation notes in the package files. Let me know if I
should remove those. [1]

Three of the packages are new and have to go through NEW. One existing package
gets new binaries and also goes through NEW? The uploads depend on each other,
so the order matters:

1. python-opentelemetry   1.45.1-2  (existing; new binaries -> NEW)
2. pydantic-handlebars    0.2.1-1   (new)        #1150536
3. python-opentelemetry-contrib
                          0.65b0-1  (new)        #1144068
4. python-logfire         5.2.0-1   (new)        #1143122
5. python-mcp             2.3.0-1   (existing; source-only upload)

The dependency chain:

- python-mcp 2.3.0 build-depends on python3-logfire for its test suite.
- python3-logfire depends on python3-opentelemetry-instrumentation (contrib)
  and on python3-opentelemetry-exporter-otlp-proto-http, which only works
  with the fixes in python-opentelemetry 1.45.1-2.
- python-logfire build-depends on pydantic-handlebars and the otel
  instrumentation (contrib) for its test suite.
- python-opentelemetry-contrib's tests use
  python3-opentelemetry-test-utils, which is a new binary in
  python-opentelemetry 1.45.1-2.


1. python-opentelemetry 1.45.1-2
   https://salsa.debian.org/python-team/packages/python-opentelemetry

Fixes #1151142. In 1.45.1-1 python3-opentelemetry-exporter-otlp-proto-http
fails to import because the modules it imports aren't shipped in any binary
package.

Changes:
- New binary packages (hence NEW):
   python3-opentelemetry-exporter-otlp-common
   python3-opentelemetry-exporter-http-transport
   python3-opentelemetry-test-utils
- Added the cross-package dependencies dh_python3 doesn't generate:
 otlp-proto-http now depends on otlp-common and http-transport, and
 otlp-proto-grpc on otlp-common. (Closes: #1151142)
- New superficial autopkgtests that install only the exporter
 package and import its modules, so a dropped dependency gets
 caught.
- Added myself to Uploaders. Not needed per se...

Known and unchanged: override_dh_auto_test runs the upstream test
suites in a shell loop that doesn't propagate failures. At the
moment it hides one sdk test that needs a bare `python` on PATH,
and the http-transport/otlp-proto-http tests that need `mocket`,
which isn't packaged. I've left this as it was. All autopkgtests
pass on 3.14 and 3.15.

2. pydantic-handlebars 0.2.1-1 (new, #1150536)
   https://salsa.debian.org/python-team/packages/pydantic-handlebars

Binaries: python3-pydantic-handlebars, pydantic-handlebars-doc.
A Handlebars template engine from the Pydantic team. Needed for
python-logfire's test suite.

3. python-opentelemetry-contrib 0.65b0-1 (new, #1144068)
   https://salsa.debian.org/python-team/packages/python-opentelemetry-contrib

Built from the upstream opentelemetry-python-contrib monorepo,
modelled on the python-opentelemetry packaging. 14 binaries:
 python3-opentelemetry-instrumentation (base)
 python3-opentelemetry-util-http
 python3-opentelemetry-instrumentation-{wsgi,asgi,django,flask,
   aiohttp-client,aiohttp-server,aws-lambda,fastapi,httpx,
   requests,system-metrics}
 python3-opentelemetry-propagator-aws-xray
python-logfire needs the base package at runtime. The
instrumentations are needed in logfire's test suite.
README.Debian explains how the multi-binary build works and how to
add more instrumentations.

I left in a lot of comments and docs. Helped me.

4. python-logfire 5.2.0-1 (new, #1143122)
   https://salsa.debian.org/python-team/packages/python-logfire

Binaries: python3-logfire, python3-logfire-api.

5. python-mcp 2.3.0-1
   https://salsa.debian.org/python-team/packages/python-mcp

New upstream version 1.28.1 -> 2.3.0. Highlights:
- Upstream declares its runtime dependencies through a uv-dynamic-
 versioning hook that we patch out. dh_python3 therefore can't see
 them, so they're listed explicitly in d/control.
- Tests are skipped on Python 3.15 for now: python3-pydantic-core
 2.50.1-2 has no 3.15 extension yet (pending its rebuild for the
 3.15 transition). Documented in README.Debian.

Reviews and comments are very welcome, and I'm happy to split this up
if that's easier for a sponsor.

Thanks,

Pieter

[1] These LLM clarification was not in my first email, so its missing in the
RFS bugs.

Attachment: signature.asc
Description: PGP signature

Reply via email to