Bug#1115742: RFS python-mcp
"Pieter Lenaerts" <[email protected]>
| Newsgroups | gmane.linux.debian.devel.wnpp |
|---|---|
| Message-ID | <DK29UAFNL5IP.2JPJEPHXT5RI6__45551.9913973816$1784436327$gmane$org@disroot.org> |
On Sat Jul 18, 2026 at 9:25 PM CEST, M. Zhou wrote: > LGTM. I'll make final checks before sponsoring the upload to NEW. Great, thanks. > 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. These are local connections. The tests start a server process and a client contacts it during the tests. If sbuild brings in a proxy variable like for auto-apt-proxy, those test want to use that proxy going to the test service. Which breaks. I feel it is ugly to patch all python packages that do local client-server tests with this to unset the proxy vars: https://salsa.debian.org/python-team/packages/python-mcp/-/blob/debian/master/debian/patches/disable_proxies_during_tests?ref_type=heads That's why I asked and maybe I should ask on mentors or on a specific thread on the debian-python list: is this the pattern to follow? Thanks, Pieter
signature.asc
(application/pgp-signature, 256 B)
-----BEGIN PGP SIGNATURE----- iIkEABYKADEWIQQrLg4/tS9aUxZMq8oFuPKwcqDg6wUCalxV6xMccGxlbmFlQGRp c3Jvb3Qub3JnAAoJEAW48rByoODrb+EA/19bjDrGUrm9vQjkLXoKQdDEZeNy0m0P PaM7CPR5SOd9APwKqvP9w+DswHopyrL1SAIL2AjEWDY/V+n32vtfukfwAw== =Yx2V -----END PGP SIGNATURE-----