On Mon, Aug 1, 2022 at 11:50 PM Nilesh Patra <[email protected]> wrote: > > On 8/1/22 8:38 PM, Shengjing Zhu wrote: > > On Mon, Aug 1, 2022 at 11:05 PM Nilesh Patra <[email protected]> wrote: > >> > >> On Mon, Aug 01, 2022 at 10:54:20PM +0800, Shengjing Zhu wrote: > >>>>> The package fails tests (see log of failing test below) when run on a > >>>>> machine with limited network (in this case: Can only reach the > >>>>> relevant APT repository server). This is a policy violation, which > >>>>> says that package tests must only access local resources services that > >>>>> were also spun up by the test. This tests tries to reach > >>>>> stun1.l.google.com though. And fails with a nil pointer dereference... > >>>> > >>>> I am not aware of any such policy -- can you please point me to it? > >>> > >>> Debian policy 4.9: > >>> > >>> For packages in the main archive, required targets must not attempt > >>> network access, except, via the loopback interface, to services on the > >>> build host that have been started by the build. > >> > >> Thanks for the link. I was under the impression that network access is > >> already > >> forbidden in the buildd environment, and package would not build if it > >> tries > >> to do so -- not sure when that changed? > > > > Because schroot doesn't implement network isolation. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802849 > > I am aware that this does not work locally because of the bug. > But one quick question - I was talking about the buildd (buildd.debian.org) > machines > here. In the wiki, it says there is 'no network' in the machines[1]. However > when I see the > setup using schroot[2]. Is it the same bug affecting it or do I miss > something (since the > package was building fine earlier anyway) > > [1]: https://wiki.debian.org/buildd#buildd_Differences > [2]: https://wiki.debian.org/BuilddSetup
Wiki is not always up to date. If you want the details, you'd better ask buildd admins, and I'm not. -- Shengjing Zhu
