-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing almond to /usr/share/jupyterlab (ie. for all users) doesn't work #729
Comments
Got some problem. |
If we want to install global, must override cache path. demo:
|
I confirmed that this solution works for jupyterhub, conda environments following the jupyterhub installation guide(the difficult way) and the command |
The solution does work. Closing. |
Hi,
I want to install almond to use it in jupyterlab. I would like to install it for all user. Unfortunately, I can't get it to work.
The issue
I want to install almond it to
/usr/share/jupyter/kernels
, instead of installing to~/.local/share/jupyter/kernels/scala
for a single user. My other kernels (like python3) are indeed located in/usr/share/jupyter/kernels
and work fine. So, I install almond with the following command:After that, I can start jupyter-lab and the option to create a scala notebook indeed appears. If I create a notebook, the kernel fails to connect (status "Connecting", then "Disconnected" at the bottom left of the web interface). In the console, I have the following error messages:
What is weird is that almond works perfectly if I install it for one user with:
Why does it matter ?
The big picture is that I am trying to fix the almond package for arch linux. When packaging, one must install in /usr/local which is the standard location for packages that all users have access to.
System
Kernel: linux-5.4.92-1-lts
Java: Oracle JDK 11 (also tried with Oracle JDK 8)
Coursier: 2.0.7, JVM version from the AUR (although I also tried with 2.0.9 native version from get-coursier)
Could you help me out with this ? Let me know if you need any additional info
Best
The text was updated successfully, but these errors were encountered: