Hi Efraim!
On 10/25/20 9:52 AM, Efraim Flashner wrote:
> On Sat, Oct 24, 2020 at 09:42:13PM +0200, Zelphir Kaltstahl wrote:
>> Hello Efraim!
>>
>> On 10/21/20 9:18 AM, Efraim Flashner wrote:
>>> On Mon, Oct 19, 2020 at 11:12:35PM +0200, Zelphir Kaltstahl wrote:
Meanwhile I have managed to run
On Sat, Oct 24, 2020 at 09:42:13PM +0200, Zelphir Kaltstahl wrote:
> Hello Efraim!
>
> On 10/21/20 9:18 AM, Efraim Flashner wrote:
> > On Mon, Oct 19, 2020 at 11:12:35PM +0200, Zelphir Kaltstahl wrote:
> >> Meanwhile I have managed to run the jupyterlab-server tests, as
> >> described in more deta
Hello Efraim!
On 10/21/20 9:18 AM, Efraim Flashner wrote:
> On Mon, Oct 19, 2020 at 11:12:35PM +0200, Zelphir Kaltstahl wrote:
>> Meanwhile I have managed to run the jupyterlab-server tests, as
>> described in more details here:
>> https://github.com/jupyterlab/jupyterlab_server/issues/128
>>
>> I
On Mon, Oct 19, 2020 at 11:12:35PM +0200, Zelphir Kaltstahl wrote:
> Meanwhile I have managed to run the jupyterlab-server tests, as
> described in more details here:
> https://github.com/jupyterlab/jupyterlab_server/issues/128
>
> Indeed, in version 1.2.0 the tests fail the same way they fail whe
On Mon, Oct 19, 2020 at 08:19:05PM +0200, Zelphir Kaltstahl wrote:
> Hello Efraim,
>
> Thanks for your patience! It seems with that I am getting quite far (at
> least it feels like making progress, or even being close to have a
> working environment), up to the "check phase". There some tests fail
Meanwhile I have managed to run the jupyterlab-server tests, as
described in more details here:
https://github.com/jupyterlab/jupyterlab_server/issues/128
Indeed, in version 1.2.0 the tests fail the same way they fail when I
try to create my environment. This means the next thing to fix would
prob
Hello Efraim,
Thanks for your patience! It seems with that I am getting quite far (at
least it feels like making progress, or even being close to have a
working environment), up to the "check phase". There some tests failing
in the "check phase". Here is what I am getting now, regardless of
whethe
It looks like you need to add python-ipykernel to native-inputs. Unless it's
needed to run the program and not just for the test suite, in which case it
should go in propagated-inputs. There's no network available in the build
environment so it can't retrieve ipykernel while building.
On Octob
Hello Efraim!
Thank you! Your idea of replacing "-" with "_" seems to partially help:
The package is downloaded and byte compiled. However, afterwards there
is a problem, when it tries to copy the byte-compiled files in the "wrap
phase" (comments inserted in some places):
START
### ... a
On Sun, Oct 18, 2020 at 01:55:49PM +0200, Zelphir Kaltstahl wrote:
> Hello Guix Users, hello Zimoun and Tobias!
>
> Thanks for your information regarding the importer syntax thing.
>
> I continued trying to get a jupyterlab environment today.
>
> Here is what I did so far:
>
> (1) Create my man
Hello Guix Users, hello Zimoun and Tobias!
Thanks for your information regarding the importer syntax thing.
I continued trying to get a jupyterlab environment today.
Here is what I did so far:
(1) Create my manifest file:
START
(specifications->manifest
'("python"))
~END~
(2)
11 matches
Mail list logo