[Debian-pan-maintainers] Unifying jupyterlab and node-jupyterlab

[Yadd]

On 6/8/24 14:06, Roland Mas wrote:
> Le 08/06/2024 à 06:15, Yadd a écrit :
>> On 6/8/24 07:25, Yadd wrote:
>>> Could you give me a way to reproduce ?
>>
>> Also retry with my last changes and dh-nodejs 0.15.22 (from 
>> https://salsa.debian.org/js-team/pkg-js-tools)
>> This version contains a /usr/bin/pkgjs which reproduces yarn or npm 
>> behavior using pkgjs-* tools. Also it creates aliases into 
>> node_modules/.bin (yarn => pkgjs, npm => pkgjs)
> 
> I pulled your changes and upgraded to dh-nodejs 0.15.22 from Git. It 
> does fix the build… but the resulting package doesn't work.
> 
> Instructions to reproduce: I do everything with git-buildpackage, in a 
> cowbuilder chroot. I set up a hook so that I get a shell within the 
> chroot after the build. Within that shell, I run "debi --with-depends" 
> to install the package, then "jupyter-lab --allow-root" to start 
> Jupyterlab; visiting http://localhost:8888/lab with a browser (even one 
> running outside the chroot) gives a blank page that says "[object 
> Module]". You can then ^C the server, then run "YARNCOMMAND=pkgjs 
> jupyter-lab build" (no need to rebuild the full package), restart the 
> server, and it still fails. But if you just run "jupyter-lab build" 
> without tweaking the YARNCOMMAND variable, then you do get a working 
> Jupyterlab.

This means that Jupyterlab needs some libraries not with the same 
version than the Debian libraries.

Test to do: "YARNCOMMAND=pkgjs PKGJS_INSTALL_OPTS=--install" to see if 
this is a missing library or an incompatible one (will ask for sudo if 
it finds some Debian libraries to install, maybe false positives)