Le 20-05-11 à 17 h 01, Nilesh Patra a écrit : > > > It's still in NEW[3]. I _think_ if you really want to enable tests now, My very bad, I forgot to check the NEW queue
> you can do the needful. Since when the packages are accepted, jest would > (hopefully) be accepted before redux, and hence that should ideally not > be a problem. > I've ran the tests with the package node-jest in the NEW queue and I had some issues with jest, some dependencies were not packaged, even by packaging them I couldn't run the tests successfully. Also the package node-jest is currently waiting for node-babel ≥ 7.8.3 [1] Therefore I tried another approach and upgraded the package node-symbol-observable to 1.2.0 instead, and upgrading node-symbol-observable to 1.2.0 works fine with a minor change in d/tests/pkg-js/test Can I upgrade the salsa package node-symbol-observable to 1.2.0? [2] > However do check the "distribution" that's experimental for jest. > If you instead want to wait for jest to be accepted, and then add tests, > that should be fine as well. > I will wait for node-jest to be at least in experimental to run redux's tests > > Yep. And that's precisely why tests are a good tool to indicate such things. > Maybe try to install redux in a chroot and test manually if things work? > I think the better approach here is to upgrade node-symbol-observable package to 1.2.0, it's the most reliable way to get a redux package compatible with upstream requirements, even if I can't run the tests at first. > > I hope that helps? > Very, thanks for the feedbacks! /Nicolas [1] - https://salsa.debian.org/js-team/node-jest/-/blob/master/debian/changelog [2] - https://salsa.debian.org/js-team/node-symbol-observable -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel