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

[Yadd]

On 5/31/24 17:10, Roland Mas wrote:
> Since I haven't managed to get 4.1 to build yet, I'm thinking of 
> starting from a known-working version (4.0.10+ds1+~cs11.25.27-1). I 
> expect that porting to 4.1 or later afterwards won't add extra work 
> compared to doing both jobs at once.
> 
> Roland.

OK, I just pushed 4.0.11 into node-jupyterlab repo (reverting your 
upgrade to 4.1.6)


> Le 30/05/2024 à 05:36, Yadd a écrit :
>> On 5/29/24 17:06, Yadd wrote:
>>> On 5/29/24 17:04, Roland Mas wrote:
>>>> Hi Yadd and others,
>>>>
>>>> I'd like to go forward with the jupyterlab/node-jupyterlab merger, 
>>>> because I'm facing more and more problems with jupyterlab/ipywidgets 
>>>> not being up-to-date. I'm going to start from node-jupyterlab (whose 
>>>> build is more complex), create a 
>>>> merge-jupyterlab-and-node-jupyterlab branch in it, and add the 
>>>> Python parts in there, starting from the current working state of 
>>>> the package (and not the current state of the master branch, which 
>>>> doesn't build since I tried to import a new upstream release). I'll 
>>>> ask for review before merging into master, but any help or advice in 
>>>> the meantime will be welcome. I'll try to be present on IRC more 
>>>> often than usual during the operation.
>>>>
>>>> Hopefully upgrading one source package will be easier after the 
>>>> merger, and I'll work on ipywidgets after that.
>>>>
>>>> Roland.
>>>
>>> hi,
>>>
>>> OK, let's do that ;-)
>>
>> From which version of jupyterlab do you want to start? 4.0.11 or later?
>>
>