Bug#770016: Clarify network access for building packages in main

2014-11-18 Thread Andrey Rahmatullin
Package: debian-policy Severity: wishlist 2.2.1 says "the packages in main must not require or recommend a package outside of main for compilation or execution (thus, the package must not declare a "Pre-Depends", "Depends", "Recommends", "Build-Depends", or "Build-Depends-Indep" relationship o

Bug#770016: Clarify network access for building packages in main

2014-11-18 Thread Charles Plessy
Le Tue, Nov 18, 2014 at 03:03:07PM +0600, Andrey Rahmatullin a écrit : > > 2.2.1 says "the packages in main > >must not require or recommend a package outside of main for compilation or > execution (thus, the package must not declare a "Pre-Depends", "Depends", > "Recommends", "Build-Depends"

Bug#770016: Clarify network access for building packages in main

2014-11-18 Thread Andrey Rahmatullin
On Tue, Nov 18, 2014 at 09:24:15PM +0900, Charles Plessy wrote: > I guess that it is implicit from the defintion of contrib that follows in > 2.2.2: > > The contrib archive area contains supplemental packages intended to work > with > the Debian distribution, but which require software outsi

Bug#770016: Clarify network access for building packages in main

2014-11-18 Thread Henrique de Moraes Holschuh
On Tue, 18 Nov 2014, Andrey Rahmatullin wrote: > On Tue, Nov 18, 2014 at 09:24:15PM +0900, Charles Plessy wrote: > > I guess that it is implicit from the defintion of contrib that follows in > > 2.2.2: > > > > The contrib archive area contains supplemental packages intended to work > > with >

Bug#770016: Clarify network access for building packages in main

2014-11-23 Thread Bill Allombert
On Tue, Nov 18, 2014 at 03:03:07PM +0600, Andrey Rahmatullin wrote: > Package: debian-policy > Severity: wishlist > > 2.2.1 says "the packages in main > >must not require or recommend a package outside of main for compilation or > execution (thus, the package must not declare a "Pre-Depends",

Bug#770016: Clarify network access for building packages in main

2014-11-23 Thread Andrey Rahmatullin
On Tue, Nov 18, 2014 at 09:24:15PM +0900, Charles Plessy wrote: > > 2.2.1 says "the packages in main > > > >must not require or recommend a package outside of main for compilation > > or > > execution (thus, the package must not declare a "Pre-Depends", "Depends", > > "Recommends", "Build-Dep

Bug#770016: Clarify network access for building packages in main

2014-11-23 Thread Andrey Rahmatullin
On Sun, Nov 23, 2014 at 05:38:50PM +0100, Bill Allombert wrote: > > Package: debian-policy > > Severity: wishlist > > > > 2.2.1 says "the packages in main > > > >must not require or recommend a package outside of main for compilation > > or > > execution (thus, the package must not declare a

Bug#770016: Clarify network access for building packages in main

2014-11-23 Thread Henrique de Moraes Holschuh
On Sun, 23 Nov 2014, Bill Allombert wrote: > --- a/policy.sgml > +++ b/policy.sgml > @@ -1928,12 +1928,16 @@ zope. > impossible to auto-compile that package and also makes it hard > for other people to reproduce the same binary package, all > required targets must be non-int

Bug#770016: Clarify network access for building packages in main

2014-11-23 Thread Bill Allombert
On Sun, Nov 23, 2014 at 10:52:54PM +0500, Andrey Rahmatullin wrote: > On Tue, Nov 18, 2014 at 09:24:15PM +0900, Charles Plessy wrote: > > > 2.2.1 says "the packages in main > > > > > >must not require or recommend a package outside of main for > > > compilation or > > > execution (thus, the p

Bug#770016: Clarify network access for building packages in main

2014-11-23 Thread Bill Allombert
On Sun, Nov 23, 2014 at 04:47:00PM -0200, Henrique de Moraes Holschuh wrote: > On Sun, 23 Nov 2014, Bill Allombert wrote: > > --- a/policy.sgml > > +++ b/policy.sgml > > @@ -1928,12 +1928,16 @@ zope. > > impossible to auto-compile that package and also makes it hard > > for other people

Bug#770016: Clarify network access for building packages in main

2014-11-23 Thread Cyril Brulebois
Bill Allombert (2014-11-23): > > This is something we want for multiple reasons, but have we already fixed > > all instances of, e.g., validating sgml/xml parsers trying to fetch DTDs or > > schemas during documentation build ? Or other network access attempts that > > don't fail a build (and hel

Bug#770016: Clarify network access for building packages in main

2014-11-23 Thread Lucas Nussbaum
On 23/11/14 at 20:03 +0100, Bill Allombert wrote: > On Sun, Nov 23, 2014 at 04:47:00PM -0200, Henrique de Moraes Holschuh wrote: > > On Sun, 23 Nov 2014, Bill Allombert wrote: > > > --- a/policy.sgml > > > +++ b/policy.sgml > > > @@ -1928,12 +1928,16 @@ zope. > > > impossible to auto-compile th

Bug#770016: Clarify network access for building packages in main

2014-11-23 Thread Bill Allombert
On Sun, Nov 23, 2014 at 08:15:33PM +0100, Lucas Nussbaum wrote: > On 23/11/14 at 20:03 +0100, Bill Allombert wrote: > > On Sun, Nov 23, 2014 at 04:47:00PM -0200, Henrique de Moraes Holschuh wrote: > > > On Sun, 23 Nov 2014, Bill Allombert wrote: > > > > --- a/policy.sgml > > > > +++ b/policy.sgml >

Bug#770016: Clarify network access for building packages in main

2014-11-24 Thread Lucas Nussbaum
On 23/11/14 at 21:13 +0100, Bill Allombert wrote: > On Sun, Nov 23, 2014 at 08:15:33PM +0100, Lucas Nussbaum wrote: > > On 23/11/14 at 20:03 +0100, Bill Allombert wrote: > > > On Sun, Nov 23, 2014 at 04:47:00PM -0200, Henrique de Moraes Holschuh > > > wrote: > > > > On Sun, 23 Nov 2014, Bill Allom

Bug#770016: Clarify network access for building packages in main

2014-11-25 Thread Jakub Wilk
[Let's leave the problem of d-i aside for the moment. I suppose it'll require a special exception in Policy, at least for the time being.] * Lucas Nussbaum , 2014-11-24, 10:21: I wonder if it should be turned into "the package must not rely on external access network to build correctly". That

Bug#770016: Clarify network access for building packages in main

2015-01-31 Thread Bill Allombert
On Mon, Nov 24, 2014 at 10:21:27AM +0100, Lucas Nussbaum wrote: > On 23/11/14 at 21:13 +0100, Bill Allombert wrote: > > Was there a lot of failure ? > > No > > > What severity did you use for the bug report ? > > serious So in practice, this is already handled as a RC bug. Good. > > Are you in

Bug#770016: Clarify network access for building packages in main

2015-02-03 Thread Lucas Nussbaum
On 31/01/15 at 20:47 +0100, Bill Allombert wrote: > On Mon, Nov 24, 2014 at 10:21:27AM +0100, Lucas Nussbaum wrote: > > On 23/11/14 at 21:13 +0100, Bill Allombert wrote: > > > Was there a lot of failure ? > > > > No > > > > > What severity did you use for the bug report ? > > > > serious > > So

Bug#770016: Clarify network access for building packages in main

2015-02-03 Thread Bill Allombert
On Tue, Feb 03, 2015 at 04:27:56PM +0100, Lucas Nussbaum wrote: > > yeah, I second this version: > > + For packages in the main archive, no required targets > > + may attempt network access. > > even if I would prefer something that did not restrict to main, and said > something

Bug#770016: Clarify network access for building packages in main

2015-02-15 Thread Bill Allombert
On Wed, Feb 04, 2015 at 10:08:50AM -0200, Henrique de Moraes Holschuh wrote: > On Tue, Feb 3, 2015, at 20:21, Bill Allombert wrote: > > On Tue, Feb 03, 2015 at 04:27:56PM +0100, Lucas Nussbaum wrote: > > > > > > yeah, I second this version: > > > > + For packages in the main archive, no r

Bug#770016: Clarify network access for building packages in main

2015-04-29 Thread Bill Allombert
On Mon, Feb 16, 2015 at 12:08:25AM +0100, Bill Allombert wrote: > On Wed, Feb 04, 2015 at 10:08:50AM -0200, Henrique de Moraes Holschuh wrote: > > On Tue, Feb 3, 2015, at 20:21, Bill Allombert wrote: > > > On Tue, Feb 03, 2015 at 04:27:56PM +0100, Lucas Nussbaum wrote: > > > > > > > > yeah, I seco

Re: Bug#770016: Clarify network access for building packages in main

2015-02-04 Thread Henrique de Moraes Holschuh
On Tue, Feb 3, 2015, at 20:21, Bill Allombert wrote: > On Tue, Feb 03, 2015 at 04:27:56PM +0100, Lucas Nussbaum wrote: > > > > yeah, I second this version: > > > + For packages in the main archive, no required targets > > > + may attempt network access. > > > > even if I would p