On Mon, Mar 04, 2024 at 09:18:01PM +0000, Julian Gilbey wrote: > [...] > So it's specifically "map" that is problematic, and I just happen to > have stumbled upon it: d3 v5 depends on d3-array version 1, but the > version of node-d3-array in unstable is 3.2.0+~cs5.0.6-2, and this is > causing the conflict. > > I don't know the best way to fix this. node-d3-array version was > upgraded from 1.2.4 to 3.x about two years ago, so d3 would have had > this bug since then, but I'm the first one to stumble upon it :-/ > > Perhaps we could package node-d3-array-1 (version 1.2.4) and have > node-d3 build-depends on that?
I was just wondering if there's a simpler way than having a new package: have d3-array 1.2.4 being an unexported component of the node-d3 source package, and instead of Build-Depends: node-d3-array, have a Build-Conflicts: node-d3-array. But then I discovered that the binary package node-d3 depends on node-d3-array, as do 7 other packages in testing (I haven't checked unstable). I'm guessing that most of those dependencies probably need version 1.x of d3-array, so it may be that having a node-d3-array-1 (or -v1) package is actually the way forward in this situation. Best wishes, Julian