Sorry for the late response.
On Sun, Apr 27, 2014, at 02:36 PM, László Böszörményi (GCS) wrote:
> On Thu, Apr 24, 2014 at 4:14 AM, Ramakrishnan Muthukrishnan
> <rkrish...@debian.org> wrote:
> > Package: libjs-d3
> > Version: 3.4.6-1
> > Severity: normal
> > I noticed that the d3.js generated by the Debian package is very
> > different from the d3.js shipped with the upstream tarball. I don't
> > know at this point, if any functionality is affected. But a simple
> > diff a lot of changes.
> I've several complex examples locally. Those works normally.
> > One of the reason for this could be that the d3 upstream package
> > requires uglify version 2.4.0 where as the d3 debian package is
> > using the one shipped with Debian, which is 1.3.4.
> Yes, this is the reason. UglifyJS does several alternations, not
> affecting the code itself. As such, the UglifyJS build dependency is
> not a hard one.
I just noticed that Jonas created a package for Uglify2 and uploaded
> > I have raised
> > a wishlist bug against the node-uglify package (#745687) requesting
> > an upgrade of the uglify package. I don't know at this point if
> > this will fix the problem.
> That would 'fix' it, ie it would look like the same to the one from
> But please note that UglifyJS 1.x  and 2.y  are different
> projects, developed differently and not an upgrade.
> I'd like to see UglifyJS2 2.y packaged as well, but it seems the
Thanks. I understand. I hope this upload will help you change the
packaging to use the uglify2. I would love to join the debian js team
and contribute. I just lack time at this point. But I surely hope to
come back and help out. A big thanks for all the work you and other
Debian JS hackers are doing to get things going.