[Debian-pan-maintainers] Jupyterlab status ?

[Roland Mas]

I updated my pbuilder chroots and tried again, and here's the simplest 
way I could find to reproduce the problem (in a clean unstable chroot):

- Build and install 4.0.11+ds1+~cs11.25.27-1 from the 
merge-python-and-node branch (currently 26d827d).

- Try running "jupyter-lab --allow-root". This command runs Jupyterlab 
based only on files that are in the package; it should display an URI at 
the end. Opening that URI in a browser leads to a simple "[object 
module]" message.

- Try building the JS components with pkgjs with the "YARNCOMMAND=pkgjs 
jupyter-lab build" command. Then run "jupyter-lab --allow-root" again, 
with similar results (error).

- Now try building the JS components without pkgjs, with the standard 
"jupyter-lab build" command. Once that is done, "jupyter-lab 
--allow-root" again, this time you get a working interface.

It should be noted that debian/rules does run the equivalent of 
"YARNCOMMAND=pkgjs jupyter-lab build" at package build time.

Roland.

Le 06/08/2024 à 18:09, Roland Mas a écrit :
> I'm having a look at that.
>
> Roland.
>
> Le 06/08/2024 à 17:23, Yadd a écrit :
>> Hi Roland,
>>
>> can you help here ?
>>
>> On 8/6/24 18:38, PICCA Frederic-Emmanuel wrote:
>>> In that case is it possible to open a bug explaining this  on the 
>>> jupyterlab package.
>>>
>>> It will be easyer for me to follow.
>>>
>>> thanks a lot
>>>
>>> Fred
>>>
>>>
>>> ----- Le 6 Aoû 24, à 16:35, Yadd yadd at debian.org a écrit :
>>>
>>>> On 8/6/24 18:18, PICCA Frederic-Emmanuel wrote:
>>>>> Sorry I hadn't seen this
>>>>> Tags: ftbfs, pending
>>>>>
>>>>> Fred
>>>>>
>>>>> If the download during the build was solved, I do not understand 
>>>>> exactly what is
>>>>> the current issue.
>>>>>
>>>>> Fred
>>>>
>>>> During jupyterlab build, extensions are compiled with
>>>> jupyter-labextension build using Debian libraries only, so no more
>>>> network connections.
>>>> The problem is that the JS result seems not usable because not build
>>>> with the compliant versions of JS dependencies.
>>>> To find and fix the problem, I need a test that proves that JS 
>>>> files are
>>>> usable. Then I've tools to detect which library is in the wrong 
>>>> version
>>>> (and then we can understand the patch to add
>>>>
>>>> @Roland, can you confirm ?
>>>>
>>>> Best regards,
>>>> Xavier
>>>
>>
>