Hi, On Mon, Feb 10, 2020 at 10:39 PM László Böszörményi (GCS) <g...@debian.org> wrote: > > Hi Paul, Balint, > > On Wed, Jan 15, 2020 at 3:51 PM Balint Reczey > <balint.rec...@canonical.com> wrote: > > On Wed, 23 Jan 2019 20:12:56 +0100 Paul Gevers <elb...@debian.org> wrote: > > > On Thu, 06 Oct 2016 22:03:43 +0200 Paul Gevers <elb...@debian.org> wrote: > > > > Upstream d3 is very active and currently runs at 4.2.6. Please consider > > > > updating the libjs-d3 package. > > > > > > Any progress on this? I'd love to have the new version in Buster. I > > > offer help if you need or want it. > There's definitely need for help, please read on.
Whenever this is the case please use Debian's standard practices to announce that: https://www.debian.org/devel/wnpp/ > > I believe the state of this package is a perfect fit for salvaging: > > https://wiki.debian.org/PackageSalvaging > It's a bit more complex situation while it's clear it's my bad that > no activity shown on this package. > > > 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. > > :-( > 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? 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 > @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 -- Balint Reczey Ubuntu & Debian Developer
