[DRE-maint] Processed: Re: ruby-uglifier: embedded code copy of uglifyJS (should depend on some package built from uglifyjs source)

Ian Jackson ijackson at chiark.greenend.org.uk
Wed Jul 27 18:00:54 UTC 2016


Debian Bug Tracking System writes ("Processed: Re: ruby-uglifier: embedded code copy of uglifyJS (should depend on some package built from uglifyjs source)"):
> Processing control commands:
> 
> > severity -1 serious
> Bug #718367 [ruby-uglifier] ruby-uglifier: embedded code copy of uglifyJS (should depend on some package built from uglifyjs source)
> Severity set to 'serious' from 'normal'
> > block -1 by 830978
> Bug #718367 [ruby-uglifier] ruby-uglifier: embedded code copy of uglifyJS (should depend on some package built from uglifyjs source)
> 718367 was blocked by: 757877
> 718367 was not blocking any bugs.
> Added blocking bug(s) of 718367: 830978

This is an interesting new example, but: Pirate, can you please
clarify what exactly your current position is, for me ?

In particular, firstly, do you now accept that the files provided in
libjs-handlebars as "source code" are not really source, because of
the facts described in #830986 (relating to parser generator output) ?

Are you therefore offering the (browserified, I assume) uglifyJS in
the ruby-uglifier source package as an additional (presumably, better)
example of the general problem you are trying get the TC to resolve in
your TC referral bug #830978 ?

If so, can you confirm that you've verified that everything in the the
copy of uglifyJS in ruby-uglifier is indeed simply a concatenation of
the original uglifyjs source (as found in the uglifyjs source
package) ?  If so, how did you perform that verification ?  If it is
not a simple concatenation, how do you know what the transformation
is ?

There are a number of other questions which came up during the
discussion of libjs-handlebars to which I don't currently know the
answers for uglifyjs and ruby-uglifier:

Is the uglifyjs in ruby-uglifier in fact itself the result of
processing by an instance of uglifyjs, or by some other tool (eg
grunt) ?

Do uglifyjs upstream accept patches which are supplied as patches to
the browserified version as found in ruby-handlebars ?

Is the uglifyjs in ruby-uglifier a browserified version of some
version of uglifyjs whose ultiate source code is (or has been) in
Debian ?

Ian.



More information about the Pkg-ruby-extras-maintainers mailing list