Bug#1144068: ITP: python-opentelemetry-contrib -- The Python auto-instrumentation libraries for OpenTelemetry
"Pieter Lenaerts" <[email protected]> Tue, 11 Aug 2026 07:09:32 +0200
| Newsgroups | gmane.linux.debian.devel.wnpp |
|---|---|
| Message-ID | <DKLUSURUB3W0.2MOAHG3U53U7H__26926.3746494957$1786425212$gmane$org@disroot.org> |
On Mon Aug 10, 2026 at 9:44 PM CEST, Carsten Schoenert wrote: > take your time I'd suggest to understand what is maintained where. > The upstream OpenTelemetry packages are quite fractured to my impression > and the git trees are very often more a collection of libraries that > should from Debian perspective live in different VCS trees. > > It took me I think more than three months to sort out things while I did > work on python-opentelemetry to get all needed information for the > packages I wanted to have and write into a proper control file. Thanks for the advice. This kind of stuff is exactly why I wanted to open the ITP before I really got into d/control and d/rules. I will take this slow and I'll see where this takes me. > [...] > Once you think you understand enough then you can dive into the Debian > packaging as some maybe in the future introduced binary packages from > the same source need get included into the build. > I want to say that d/rules needs to get constructed flexible enough to > get this later handled easily. Then start with the easiest to package > project. I will come back for advice once I know more. Thanks again! Pieter
signature.asc
(application/pgp-signature, 256 B)
-----BEGIN PGP SIGNATURE----- iIkEABYKADEWIQQrLg4/tS9aUxZMq8oFuPKwcqDg6wUCanqujRMccGxlbmFlQGRp c3Jvb3Qub3JnAAoJEAW48rByoODrOcAA/iKdI254Vk21Gc7JKX88UIB2LwjhCkLR lfxIDKlFHvShAP9PUmnRUm1KY2Dk8DFQsemIRMme4yL/8dXOFi5sw0mqDg== =hBR9 -----END PGP SIGNATURE-----