Re: Bug#1104643: Don't consider tests during build that can use internet if available as rc buggy

[Andrey Rakhmatullin <wrar@debian.org>]

On Mon, May 05, 2025 at 11:19:09AM +0200, Bill Allombert wrote:
> > Current policy text says:
> >
> > > Except for packages in the non-free archive with the Autobuild control
> > field unset or set to no,
> > > 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.
> >
> > I think it should be changed to,
> >
> > > Except for packages in the non-free archive with the Autobuild control
> > field unset or set to no,
> > > required targets must not require network access, except, via the loopback
> > interface,
> > > to services on the build host that have been started by the build.
> >
> > I think enforcing there is no internet access is a better way to achieve the
> > goal of actually ensuring there is no internet during build rather than
> > considering packages that can use internet when available for tests as rc
> > buggy.
>
> I disagree. This was not the consensus at the time I made this change to policy, and
> I do not think it is the consensus now. We want more reproducible builds, not
> depending on external resources that are bound to change, and not being tracked via
> server logs. 

As the submitter of #770016 I agree.


--
WBR, wRAR

Attachment: signature.asc
Description: PGP signature