Package Details: jupyterhub 5.2.1-1

Git Clone URL: https://aur.archlinux.org/jupyterhub.git (read-only, click to copy)
Package Base: jupyterhub
Description: Multi-user server for Jupyter notebooks
Upstream URL: https://jupyter.org/hub
Licenses: BSD-3-Clause
Submitter: xantares
Maintainer: bcb
Last Packager: bcb
Votes: 9
Popularity: 0.000000
First Submitted: 2015-03-12 14:00 (UTC)
Last Updated: 2024-11-21 15:30 (UTC)

Sources (3)

Pinned Comments

bcb commented on 2021-12-05 16:27 (UTC)

Note that version upgrades may require you to upgrade the database before the new version will start. Always check the documentation, in particular the changelog before upgrading.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

bcb commented on 2021-12-05 16:25 (UTC)

I have just updated the package to 2.0.0. I have included a patch which changes some of the tests to use random ports so they will not fail if you already have a JupyterHub server running. A handful of tests are disabled because they are not compatible with this patch or I couldn't find a way to make them work with random port numbers. When I get time I will try to work with upstream to get the tests modified properly for this.

dodecahedron commented on 2021-12-03 18:11 (UTC)

This package is already marked out of date, but FYI, 2.0.0 is now out too: https://github.com/jupyterhub/jupyterhub/releases/tag/2.0.0

leuko commented on 2021-05-02 19:28 (UTC)

found the source :D

My Jupyterhub instance was already running on port 8000, so most of the tests failed. Maybe a short warning could be useful, what do you think @bcb?

leuko commented on 2021-05-02 19:21 (UTC)

Thank you for testing out @bcb! I just tried on another machine, and it works.

On my server somehow most of the tests fail, but makepkg --nocheck works. I will compare the build logs then. You do not have to wait for me, thanks :J

bcb commented on 2021-05-02 09:46 (UTC)

@leuko: The tests (including the one you mentioned) pass on two different machines for me, including in a clean chroot with just the package dependencies. It could be an interaction with another package you have installed I guess. Does jupyterhub run if you skip the checks (makepkg --nocheck)? Can you you upload the full build log from one of these failures to a pastebin and post the link here?

And thanks for pointing out the pycurl optional dependency. I'll add it to the PKGBUILD -- I'll wait a little while before I upload a new PKGBUILD in case we can figure out something for the check failures in the same upload.

leuko commented on 2021-04-28 05:24 (UTC)

I get a lot of errors during check(), e.g.,

jupyterhub/tests/test_proxy.py::test_add_get_delete[host.name/path/] ERROR

and many tornado.httpclient.HTTPClientError: HTTP 403 errors. Does someone else have this problem?

leuko commented on 2021-04-28 05:20 (UTC)

python-pycurl seems to be an optional dependency

bcb commented on 2021-04-26 17:35 (UTC)

@lonaowna glad it wasn't too hard to solve. I've started a wiki page at https://wiki.archlinux.org/index.php/JupyterHub and have added some details about file permissions to the section on the PAM authenticator.

lonaowna commented on 2021-04-26 16:15 (UTC)

@bcb spot on! Turns out my /etc/shadow had permissions 000 instead of 600. No idea how that happened. After fixing that, jupyterhub works with just CAP_SETUID CAP_SETGID. Thanks so much!

bcb commented on 2021-04-26 07:01 (UTC)

So its a file permissions problem. What are the file permissions on /etc/shadow? It needs to be able to read that to check the password.

The PAM authenticator uses the pamela library to perform the authentication, and the library can be used from the command line. If you do sudo su - to get a root shell, and then python -m pamela -a <regular username> in that root shell, does the authentication succeed?

« First ‹ Previous 1 2 3 4 5 6 Next › Last »