[Pkg-javascript-devel] node-expat is marked for autoremoval from testing

2016-10-07 Thread Debian testing autoremoval watch
node-expat 2.3.12-1 is marked for autoremoval from testing on 2016-10-24

It (build-)depends on packages with these RC bugs:
837285: node-iconv: FTBFS: Tests failures


-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] node-body-parser is marked for autoremoval from testing

2016-10-07 Thread Debian testing autoremoval watch
node-body-parser 1.8.1-1 is marked for autoremoval from testing on 2016-10-24

It (build-)depends on packages with these RC bugs:
837285: node-iconv: FTBFS: Tests failures


-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] node-iconv is marked for autoremoval from testing

2016-10-07 Thread Debian testing autoremoval watch
node-iconv 2.1.11-1 is marked for autoremoval from testing on 2016-10-24

It is affected by these RC bugs:
837285: node-iconv: FTBFS: Tests failures


-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] node-raw-body is marked for autoremoval from testing

2016-10-07 Thread Debian testing autoremoval watch
node-raw-body 1.2.0-1 is marked for autoremoval from testing on 2016-10-24

It (build-)depends on packages with these RC bugs:
837285: node-iconv: FTBFS: Tests failures


-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel


[Pkg-javascript-devel] ltx is marked for autoremoval from testing

2016-10-07 Thread Debian testing autoremoval watch
ltx 2.4.2-1 is marked for autoremoval from testing on 2016-10-24

It (build-)depends on packages with these RC bugs:
837285: node-iconv: FTBFS: Tests failures


-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel


Re: [Pkg-javascript-devel] jquery-goodies policy and grunt

2016-10-07 Thread Jonas Smedegaard
Quoting Paul Gevers (2016-10-07 15:33:39)
> First off, you voice my opinion, and fortunately you don't mention 
> anything new (to me). The reason why I asked is because what I observe 
> in packages maintained by this team (which is new to me).

This team is very loose - which means some in the team package in a 
style others do not agree with.


> On 07-10-16 15:21, Jonas Smedegaard wrote:
>> Quoting Paul Gevers (2016-10-07 14:09:43)
>>> A relate question: JavaScripts are often "combined" with Grunt. What 
>>> is the current status/stance of including those in Debian.
>
> You didn't really answer this question. As far as I am aware, but 
> maybe I am wrong, there were issues with getting Grunt into Debian. Or 
> is that issue already solved.

Sorry if I was unclear.

In my *personal* opinion, concatenated source is not upstream preferred 
form and therefore not the ideal for us to redistribute as source and 
therefore not something that I personally would treat as such.

I believe we as *team* do not have different rules than Debian in 
general regarding what is permitted and what is not in source packages.

No, grunt was not in Debian last I checked.  What I would do is try 
mimic with other tools what grunt does.  I would so such mimicing during 
*build* from true non-concatened non-minified sources included in source 
package, due to my personal opinion described above.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] jquery-goodies policy and grunt

2016-10-07 Thread Paul Gevers
Hi Jonas,

First off, you voice my opinion, and fortunately you don't mention
anything new (to me). The reason why I asked is because what I observe
in packages maintained by this team (which is new to me).

On 07-10-16 15:21, Jonas Smedegaard wrote:
> Quoting Paul Gevers (2016-10-07 14:09:43)
>> A relate question: JavaScripts are often "combined" with Grunt. What 
>> is the current status/stance of including those in Debian.

You didn't really answer this question. As far as I am aware, but maybe
I am wrong, there were issues with getting Grunt into Debian. Or is that
issue already solved.

Paul



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] jquery-goodies policy and grunt

2016-10-07 Thread Jonas Smedegaard
Hi Paul,

Quoting Paul Gevers (2016-10-07 14:09:43)
> I am about to add some JavaScript binary packages to Debian, but I was 
> really wondering what the current ideas are with respect to source 
> packages. There are a lot of jquery plugins packaged in the 
> jquery-goodies package, but also several (a lot?) of plugins are 
> packaged separately. What is the current consensus: should new plugins 
> be packages via the jquery-goodies package or stand-alone or does it 
> depend? Are there reasons to choose one or the other?

You should track each upstream project.

Easiest way to do that is to package each (real!) upstream as a separate 
Debian source package.

You might alternatively track indirectly either via an intermediate 
pseudo-upstream or via bundling multiple upstream into a single Debian 
source package - but I doubt that will work reliably, and continue to do 
so over time.  And I doubt it works well for current bundle packages!


> A relate question: JavaScripts are often "combined" with Grunt. What 
> is the current status/stance of including those in Debian. I am 
> normally of the opinion that everything should be build from source, 
> but I can also be somewhat pragmatic if required. JavaScript that is 
> combined is still very readable and changeable and I have the idea 
> that there is a lot of JavaScript in Debian that isn't "build from 
> source".

You must include source.

Easiest way to do that is to only include source - i.e. the form 
preferred by (real!) upstream as basis for their development.

You might alternatively ensure in other ways that source is included, 
e.g. by build-depending on other packages shipping the source and 
implementing build rules checking that processing (minifying, 
concatenation, whatever) of both real source and your included files 
produce identical result.  But I am highly sceptical that it will be 
simpler, or that you can come up with an approach that ftpmasters, 
release managers, and Debian in general will agree complies with DFSG 
if/when they actually look closely at what you implement (but obviously 
you might succeed at first with getting it into Debian if they don't).


Hope that helps.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] jquery-goodies policy and grunt

2016-10-07 Thread Paul Gevers
Hi all,

I am about to add some JavaScript binary packages to Debian, but I was
really wondering what the current ideas are with respect to source
packages. There are a lot of jquery plugins packaged in the
jquery-goodies package, but also several (a lot?) of plugins are
packaged separately. What is the current consensus: should new plugins
be packages via the jquery-goodies package or stand-alone or does it
depend? Are there reasons to choose one or the other?

A relate question: JavaScripts are often "combined" with Grunt. What is
the current status/stance of including those in Debian. I am normally of
the opinion that everything should be build from source, but I can also
be somewhat pragmatic if required. JavaScript that is combined is still
very readable and changeable and I have the idea that there is a lot of
JavaScript in Debian that isn't "build from source".

Paul



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel