On Oct 03, Gunnar Wolf wrote:
> So, contrib is _explicitly_ meant for software that does not meet the
> DFSG, not for random stuff that cannot be packaged for convenience or
> different issues.
I am almost sure that when I joined the project contrib was also the
place for
Sean Whitton writes:
> Hello Jérémy,
>
> On Tue, Oct 03 2017, Jérémy Lal wrote:
>
>> It might be a good idea to make policy more explicit about downloads
>> during build.
>
> I'm not sure how it could be more explicit:
>
> For packages in the main archive, no
Pirate Praveen writes ("Re: [Pkg-javascript-devel] Bug#877212: node-d3-color:
B-D npm not available in testing"):
> Lets take the two issues separately.
>
> 1. Whether they are suitable for contrib
I don't think that this is what contrib is for. Contrib exists as
par
On ബുധന് 04 ഒക്ടോബര് 2017 02:07 വൈകു, Philip Hands wrote:
> The problem seems to be that Praveen reads that prohibition as implying
> that it is totally OK to do this when not in main.
>
> This strikes me as equivalent to reading:
>
> All men are mortal,
> Socrates is a man,
>
> and
On 10/04/2017 05:50 AM, Sean Whitton wrote:
> Hello Jérémy,
>
> On Tue, Oct 03 2017, Jérémy Lal wrote:
>
>> It might be a good idea to make policy more explicit about downloads
>> during build.
> I'm not sure how it could be more explicit:
>
> For packages in the main archive, no required
Hello Pirate,
On Tue, Oct 03 2017, Pirate Praveen wrote:
> Alternatively, those who care enough about the issue can help get
> these tools into main. I have been doing just that over the last years
> (grunt, gulp, babel, jison, webpack to name a few, each with 100s of
> dependencies) so many of
Hello Jérémy,
On Tue, Oct 03 2017, Jérémy Lal wrote:
> It might be a good idea to make policy more explicit about downloads
> during build.
I'm not sure how it could be more explicit:
For packages in the main archive, no required targets may attempt
network access.
--
Sean Whitton
Jérémy Lal dijo [Tue, Oct 03, 2017 at 07:46:43PM +0200]:
> It might be a good idea to make policy more explicit about downloads during
> build.
I completely agree. This led me to look at #813471 ("network access to
the loopback device should be allowed"), and... Well, it seems to set
the stage to
2017-10-03 19:34 GMT+02:00 Gunnar Wolf :
> Pirate Praveen dijo [Tue, Oct 03, 2017 at 12:12:54PM +0530]:
> > > I am completely with Sean here; I read the following messages, and am
> > > happy a better resolution was found. But, FWIW, I'll support Sean's
> > > interpretation -
Hello,
On Sat, Sep 30 2017, Christian Seiler wrote:
> Ack. Wouldn't it be preferable to just include a copy of the prebuilt
> node-d3-color "binary" alongside its actual source tarball and have
> debian/rules just copy the prebuilt "binary" for now? That would
> fulfill one of the widely
Hello Pirate,
On Sun, Oct 01 2017, Pirate Praveen wrote:
> On 09/30/2017 09:26 PM, Sean Whitton wrote:
>> To my mind, this complies with the letter of Policy but not its
>> spirit.
>
> The whole purpose of having contrib and non-free is to host packages
> that can't be in main, either
On 09/30/2017 01:30 PM, Andreas Beckmann wrote:
> Unstable is not outside the archive.
But that dos not seem logical. Does it mean these packages can stay in
testing if we remove npm from unstable?
signature.asc
Description: OpenPGP digital signature
--
Pkg-javascript-devel mailing list
On വെള്ളി 29 സെപ്റ്റംബര് 2017 10:54 വൈകു, Andreas Beckmann wrote:
> Hi,
>
> with npm not available in testing (and according to #857986 this will
> not change in the near future), these node-* packages must be kept
> out of testing, since they cannot be rebuilt in testing (regardless of
> any
2017-09-29 19:24 GMT+02:00 Andreas Beckmann :
> Package: node-d3-color
> Version: 1.0.3-1
> Severity: serious
> Justification: Build-Depends not satisfiable in testing
> Control: block -1 with 857986
> Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
> Control: reassign -2
14 matches
Mail list logo