#839961 libjs-d3: please package new upstream release

Package:
libjs-d3
Source:
d3
Submitter:
Paul Gevers
Date:
2022-07-07 20:24:03 UTC
Severity:
wishlist
#839961#5
Date:
2016-10-06 20:03:43 UTC
From:
To:
Dear maintainer,

Upstream d3 is very active and currently runs at 4.2.6. Please consider
updating the libjs-d3 package.

My next upstream version of cacti depends on libjs-d3, but includes a much
newer version that I rather not ship.

Thanks for considering
Paul

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

- -- no debconf information
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJX9q4fAAoJEJxcmesFvXUKjNYH/Ah9WlPmB7owYXsry7zVW2Lu
g+x0Y/WpMeF5v5fVc7q6jkVp5lDXIEagte15vd26tShTyzpbB+zxPYgNyDdzwSwy
cY8T8ReMmAB1cg3cYcCqc0FL4GpySuGV7WxHG6MiWDo37WM5Fbvaj2o3djFJFclF
01bfO5iuZBZKzre1bTfuWhs8AWX63eaVnlBFOTOZQXBPgU62z/PsIlUHBGusQfiz
tqXDJvkC3qDLDPRmX+o+UxKZDm6kA0wk3KvFJ1KDN94RW5eZZhZ4SYR1i335Wpjj
9r3EjoL/eBZWdSs9Ij1TS6GXqVhJfFHp1TXwCqK+SPy3n58tGWeRRsBvNIpRQ8U=
=ico0
-----END PGP SIGNATURE-----
#839961#10
Date:
2016-12-08 07:06:50 UTC
From:
To:
Note, I am told by its authors that coz depend on libjs-d3 too, but do not
work with version 4 as it has a different API.
#839961#15
Date:
2018-09-15 20:52:58 UTC
From:
To:
Hi,

libjs-d3 in Debian has not been updated for more than 2 years.
Version 3.5.17 isn't really very useful.
Please consider updating it, or perhaps officially orphan it if
you are no longer able to maintain it.


Thanks, Phil.
#839961#22
Date:
2019-01-23 19:12:56 UTC
From:
To:
Hi,

Any progress on this? I'd love to have the new version in Buster. I
offer help if you need or want it.

Paul
#839961#27
Date:
2020-01-15 14:45:48 UTC
From:
To:
Hi Paul and Laszlo,
https://wiki.debian.org/PackageSalvaging

I'd like to have a fresh d3 in next Ubuntu LTS and also in Bullseye,
but I don't have enough free time now to salvage the package myself.
:-(

Cheers,
Balint
#839961#32
Date:
2020-02-10 21:39:25 UTC
From:
To:
Hi Paul, Balint,

On Wed, Jan 15, 2020 at 3:51 PM Balint Reczey <balint.reczey@canonical.com> wrote:
 There's definitely need for help, please read on.
 It's a bit more complex situation while it's clear it's my bad that
no activity shown on this package.
 Wanted to go into details, but let me be brief now. When I packaged
D3.js it was one source tree only with dependencies packaged. Then its
build system switched to rollup, not packaged back then. With time it
further evolved and became highly modularized, meaning multiple source
tarballs.
Currently it has 45 (forty-five) modules, depending on each other like
a tree structure. Random check showed at least one of these has
unpackaged other JavaScript dependency. In really short, just see the
top level D3.js dependency list[1] which shows 31 (thirty-one)
immediate D3 modules dependency. That means about 50+ (fifty+)
JavaScript packages need to be created, uploaded and accepted to the
archives.
Do you know anyone who can take such a huge task?
@Balint: What's the best way to talk with you in personally? A meeting
or a phone call would do; maybe a chat on some platform.

Regards,
Laszlo/GCS
[1] https://github.com/d3/d3/blob/master/package.json
#839961#37
Date:
2020-02-11 06:29:45 UTC
From:
To:
 Just for the record, did a quick check for the current situation.
Most important JavaScript dependencies are packaged and seems new
enough (not always the latest upstream version but lagging behind).
The eslint[1] need to enter the normal archive as it's only in
experimental only. Then rollup-plugin-terser[2] should be packaged,
even if it doesn't look like a hard dependency.
D3.js can be packaged via the following packages.
1) d3-array, d3-color, d3-dsv, d3-ease, d3-path, d3-polygon, d3-queue,
d3-selection, d3-time, d3-timer, d3-voronoi
2) d3-collection, d3-contour, d3-fetch, d3-format, d3-interpolate,
d3-quadtree, d3-random, d3-shape, d3-time-format
3) d3-geo, d3-scale, d3-hierarchy, d3-scale, d3-scale-chromatic, d3-transition
4) d3 itself

Not needed ATM: d3-cam16, d3-delaunay, d3-force, d3-geo-polygon,
d3-geo-projection, d3-hcg, d3-hexbin, d3-hsv, d3-request, d3-require,
d3-sankey, d3-scripts, d3-selection-multi, d3-tile, d3-zoom

Regards,
Laszlo/GCS
[1] https://packages.qa.debian.org/eslint
[2] https://www.npmjs.com/package/rollup-plugin-terser
#839961#42
Date:
2020-03-03 15:04:21 UTC
From:
To:
Hi,

On Mon, Feb 10, 2020 at 10:39 PM László Böszörményi (GCS) <gcs@debian.org> wrote:

Whenever this is the case please use Debian's standard practices to
announce that:
https://www.debian.org/devel/wnpp/

This is a very good question in general, and the immediate answer is
not "It's me!" from the maintainer (or "It's us!" in case of a team
maintaining the package) then I'd recommend looking for help in
maintenance.
For this particular package I'd recommend bringing it under the Debian
Javascript Maintainers Team's umbrella who already maintain node-d3
which has v5 in experimental.

Cheers,
Balint
#839961#47
Date:
2022-04-11 19:50:47 UTC
From:
To:
Hi László,

On Mon, 10 Feb 2020 22:39:25 +0100 =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= <gcs@debian.org> wrote:

I just spotted the node-d3 package. Has that solved all the issues and
can that be considered the replacement of this package?

If so, should libjs-d3 be removed from Debian?

Paul