[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2208: excluded from Debian because of no-source-code-included files

[Tahoe-LAFS]

#2208: excluded from Debian because of no-source-code-included files
---------------------------+---------------------------
     Reporter:  zooko      |      Owner:  zooko
         Type:  defect     |     Status:  new
     Priority:  critical   |  Milestone:  1.11.0
    Component:  packaging  |    Version:  1.10.0
   Resolution:             |   Keywords:  review-needed
Launchpad Bug:             |
---------------------------+---------------------------

Comment (by vu3rdd):

 Daira and I had a chat on the IRC today. I tried a few things today, here
 is the summary:

 - The d3.js shipped with Debian's libjs-d3 package is different from the
 upstream d3.js.
 - If I download the source and build it with 'npm install' and then 'make'
 (along with the Debian's nodejs package), it produces exactly the same js
 file as the one shipped with the upstream.
 - Upon further inspection, looks like the uglify.js (I don't know what it
 does!) shipped with Debian and used by the libjs-d3 is quite old. D3
 upstream needs 2.4.0 where as Debian has 1.3.4. Perhaps this needs to be
 fixed. I will raise a debian bug regarding this.
 - I tried changing the dev dependency of the upstream sources of d3 to
 match that of the debian's dependency and build it but it didn't build for
 me with some weird error, which I didn't pursue further.

 I wonder what can be done at this point. If Debian's current version of D3
 and JQuery libraries work fine, then I could quickly change/patch the
 XHTML source to use those files in Debian (/usr/share/javascript/*), add
 dependencies on those libraries and do an upload. Alternatively, I could
 add a patch that removes the d3.min.js and jquery.min.js and add the non-
 minified versions.

 Comments?

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2208#comment:28>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage