mbedtls is required now I guess. I was not abled to start Julia kernel without it, it goes into a infinite loop.
Search Criteria
Package Details: jupyterlab-git 1:3.0.0.r0.g63c5989cdd-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/jupyterlab-git.git (read-only, click to copy) |
---|---|
Package Base: | jupyterlab-git |
Description: | JupyterLab computational environment |
Upstream URL: | https://github.com/jupyterlab/jupyterlab |
Keywords: | jupyter notebook python |
Licenses: | custom |
Submitter: | fabianz |
Maintainer: | None |
Last Packager: | fusion809 |
Votes: | 4 |
Popularity: | 0.000000 |
First Submitted: | 2016-07-31 22:21 (UTC) |
Last Updated: | 2020-12-24 01:29 (UTC) |
Dependencies (7)
- jupyterlab_server
- jsx-lexerAUR (make)
- nodejs (nodejs-lts-fermiumAUR, nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogen, nodejs-lts-iron) (make)
- python-recommonmarkAUR (make)
- python-setuptools (make)
- python-sphinx-copybutton (make)
- python-sphinx_rtd_theme (make)
Required by (1)
- jupyter-octave_kernel-git (optional)
Sources (2)
Latest Comments
« First ‹ Previous 1 2 3
j605 commented on 2018-02-28 00:22 (UTC)
j605 commented on 2018-02-20 18:09 (UTC)
The maintainer of jupyterlab has not updated their package and commented on the package asking for someone to take over. Can you take over the stable release.
fabianz commented on 2018-02-19 15:39 (UTC)
Updated PKGBUILD for upstream build process changes. Due to larger upstream change, I'd gladly welcome any testing of the new package.
@flying-sheep Thanks for providing the updated PKGBUILD in the meantime! JupyterLab seems to be quite a moving target in regard to packaging - unfortunately, your updates were already obsoleted again.
flying-sheep commented on 2017-04-20 13:01 (UTC) (edited on 2017-04-20 13:43 (UTC) by flying-sheep)
OK, got it working.
https://gist.github.com/flying-sheep/d6eea15f8a6075f988672eccdddf4bfc
the pure python package as built by the current PKGBUILD is pretty useless. i don’t understand how it can work for any of you.
did they shipped prebuilt stuff before?
flying-sheep commented on 2017-04-20 11:52 (UTC) (edited on 2017-04-20 12:00 (UTC) by flying-sheep)
this should be done as part of the package just like i do here:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=jupyter_contrib_nbextensions
only woth the command
env ... jupyter serverextension enable --py jupyterlab --user
the problem here is that /etc/jupyter/jupyter_notebook_config.json will exist in both packages.
we’ll need to use something like http://jsonpatch.com and an .install file to unify both.
uberscientist commented on 2016-11-18 14:19 (UTC)
the 404 issue that I ran into as well can be fixed by enabling the jupyterlab extension:
$jupyter serverextension enable --py jupyterlab --user
source: https://github.com/jupyterlab/jupyterlab/issues/1187#issuecomment-257872472
juliohm commented on 2016-10-20 18:10 (UTC)
My bad @fabianz, I think the issue was that I was using Jupyter by the time I tried to run jupyter lab in the command line. I closed Jupyter and everything is working perfectly. Thank you for this package!
fabianz commented on 2016-10-20 11:28 (UTC)
I just rebuilt from master, everything is working fine for me. Running 'jupyter lab' gives me (among others) the following log line:
[I 13:10:22.796 LabApp] The Jupyter Notebook is running at: http://localhost:8888/
It opens my default browser (Firefox) with the given url and JupyterLab is usable without issues.
First thought: Do you run some other HTTP server on port 8888?
If that's not the case, could you run 'jupyter lab --debug' and upload the output (using e.g. some pastebin service), giving a link to it here. That may help investigating.
Regarding the usage of pip: I like to keep everything managed by pacman - pip is essentially a different package manager and using it without a python venv may leave you with files untracked by pacman, potentially leading to package problems. See also https://bbs.archlinux.org/viewtopic.php?id=139264
juliohm commented on 2016-10-20 05:35 (UTC)
When I try to launch JupyterLab with "jupyter lab" in the command line, I get a new tab in Chrome with:
404 : Not Found
You are requesting a page that does not exist!
Could you please confirm this is an issue of the master branch? Would it be safe to install the lab with pip?
Pinned Comments
fusion809 commented on 2020-07-07 12:09 (UTC)
In case anyone is wondering, yes I am well aware that there is a build error at the moment, but a bug report for it exists upstream https://github.com/jupyterlab/jupyterlab/issues/8657, and there's nothing I can do about it downstream until they fix it upstream.