On Sun, 28 Jun 2026 10:21:50 +0200 "Pieter Lenaerts" <[email protected]> wrote: > Dear Python team,
> Package is at https://salsa.debian.org/python-team/packages/python-mcp > > There was an ITP bug at > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115742 > > Can someone please review my work? If its fine, upload it or give me upload > rights? Not sure if that can work on new packages? LGTM. I'll make final checks before sponsoring the upload to NEW. > Two questions I have: > 1. I added a man page. I created that from markdown, but to keep pandoc out > of the > build process I manually converted the md to troff and kept both in the debian > dir. Is that fine or should I build the troff file from my markdown source? It is fine. > 2. I now have the second package that uses network calls during tests. They > break in gbp buildpackage because I use auto-apt-proxy. I work around that > with > a fixture unsetting HTTPS?_PROXY env vars. Is that the way to go? I doubt we > want to bother all upstream packages to unset HTTPS?_PROXY vars like that? Debian policy disallows network access during required targets: https://www.debian.org/doc/debian-policy/ch-source.html It is not likely network is accessible with within buildd. If it fails, simply skip the tests that requires network access.
