[IPython-dev] Jupyter Hub Doc Issue

MinRK benjaminrk at gmail.com
Sat Feb 7 18:08:18 EST 2015


I haven’t tried setting up JupyterHub on old Ubuntu, but I would expect it
to be a bit of a pain, given the requirements of recent versions of things.
I would expect Ubuntu 12.04 to need one or more PPAs, or to use non-apt
installations for more recent dependencies.

The reason for the nodejs-legacy package is that the node executable was
taken by a package nobody uses, and debian renamed the executable nodejs
instead of node. This actually results in a totally non-functional node
environment, so a bit of an odd choice. The nodejs-legacy is a separate
package that makes the node executable point to nodejs. It is probably that
a nodejs PPA installs the more standard node executable, obviating the need
for nodejs-legacy.

I think adding caveats for installation on older or less common systems is
worthwhile as people come across them. Perhaps the better content for our
docs is to be more terse, and say “require nodejs >= 0.10”, and just link
to node’s own docs for installation, since we are no experts on getting a
nodejs environment set up, just like I don’t think it’s the responsibility
of every Python package to have detailed docs on how to install Python.
Certainly explaining *why* the nodejs-legacy package is required on recent
Ubuntu/Debian should make it clearer that it may not be relevant if you
choose a different path to installing node.

-MinRK
​

On Sat, Feb 7, 2015 at 6:33 AM, John Omernik <john at omernik.com> wrote:

> That makes sense. I am trying to get a sense for things from a infosec
> standpoint, as to contributing to the wiki, I would very much be in
> favor of this, however, I don't feel I have the expertise right now to
> contribute to it. The reason I post here, is I can toss out what I
> did, and my assumptions and even if that's wrong, someone will likely
> call me out, that way I can learn from it, and anyone facing the same
> issues can learn too. I don't want my assumptions to be taken as word
> in the documentation.
>
> On Sat, Feb 7, 2015 at 8:04 AM, Doug Blank <doug.blank at gmail.com> wrote:
> > On Sat, Feb 7, 2015 at 8:34 AM, John Omernik <john at omernik.com> wrote:
> >>
> >> After more research (not in the jupyter docs) I realized that the link
> >> Wes provided actually contradicts the Jupyter Hub documentation. Hence
> >> why I posted. For anyone having issues with the Jupyter Docs, you
> >> nodejs-legacy doesn't work on Ubuntu 12.04, so you have to add the PPA
> >> in the link Wes provided.  However then, there is a note about apt-get
> >> install npm, which will not work with the PPA Wes provided, because of
> >> a version conflict and because npm is included in the nodejs package
> >> from Wes' link.
> >>
> >> Wes: Appreciate the reply, but I think the documentation could use
> >> some work, and throwing links at people who ask questions based on the
> >> current documentation may produce more frustration especially when the
> >> links you provide don't line up with the documentation the user is
> >> trying to install.  I am not upset, I am just pointing out that some
> >> users may get frustrated (I am not one of those, but I have worked
> >> with many like that).
> >
> >
> > The jupyterhub docs are a wiki, so do please contribute and add to those.
> >
> > Jupyterhub is a bit different from other IPython projects in that it can
> be
> > an exposed server application. Deploying it incorrectly can open your
> system
> > up in unwanted ways.  On one hand, one needs to have some experience in
> > running a web server.
> >
> > On the other hand, it is also "fairly easy" to get setup for us
> non-admins.
> > However, there are a million variations depending on OS and local setup.
> >
> > So, the docs will never be complete. I think I good goal would be to
> make it
> > as comprehensive as possible for a limited set of standard operating
> > systems/distributions. I suggest targeting Ubuntu 14.04 Long Term Service
> > (LTS) for documentation would be a good compromise. Of course, it could
> be
> > deployed in many more ways, but having a single well-documented example
> > might provide hints for others.
> >
> > -Doug
> >
> >>
> >>
> >> Thanks!
> >>
> >> John
> >>
> >>
> >>
> >> On Sat, Feb 7, 2015 at 4:55 AM, John Omernik <john at omernik.com> wrote:
> >> > As a follow-up, I did the above top link to install repository, now
> >> > when I try to do npm, I get:
> >> >
> >> > sudo apt-get install npm
> >> >
> >> > Reading package lists... Done
> >> >
> >> > Building dependency tree
> >> >
> >> > Reading state information... Done
> >> >
> >> > Some packages could not be installed. This may mean that you have
> >> >
> >> > requested an impossible situation or if you are using the unstable
> >> >
> >> > distribution that some required packages have not yet been created
> >> >
> >> > or been moved out of Incoming.
> >> >
> >> > The following information may help to resolve the situation:
> >> >
> >> >
> >> > The following packages have unmet dependencies:
> >> >
> >> >  npm : Depends: nodejs but it is not going to be installed
> >> >
> >> >        Depends: nodejs-dev
> >> >
> >> >        Depends: node-request but it is not going to be installed
> >> >
> >> >        Depends: node-mkdirp but it is not going to be installed
> >> >
> >> >        Depends: node-minimatch but it is not going to be installed
> >> >
> >> >        Depends: node-semver but it is not going to be installed
> >> >
> >> >        Depends: node-ini but it is not going to be installed
> >> >
> >> >        Depends: node-graceful-fs but it is not going to be installed
> >> >
> >> >        Depends: node-abbrev but it is not going to be installed
> >> >
> >> >        Depends: node-nopt but it is not going to be installed
> >> >
> >> >        Depends: node-fstream but it is not going to be installed
> >> >
> >> >        Depends: node-rimraf but it is not going to be installed
> >> >
> >> >        Depends: node-tar but it is not going to be installed
> >> >
> >> >        Depends: node-which but it is not going to be installed
> >> >
> >> > E: Unable to correct problems, you have held broken packages.
> >> >
> >> >
> >> >
> >> > On Sat, Feb 7, 2015 at 4:52 AM, John Omernik <john at omernik.com>
> wrote:
> >> >> Thank you Wes I am trying that.
> >> >>
> >> >> That said, when the documentation says do this "nodejs-legacy" and it
> >> >> doesn't work, as an end user you wonder "well, wait, that isn't what
> I
> >> >> was told to install, yes I could just install from this other
> >> >> repository,but  that isn't what the documentation calls for, but will
> >> >> it be what the Jupyter Hub requires? Will it sorta work and possibly
> >> >> provide me other issues that I have to spend time on, etc.   Just an
> >> >> observation as an end user.
> >> >>
> >> >> On Fri, Feb 6, 2015 at 11:03 PM, Wes Turner <wes.turner at gmail.com>
> >> >> wrote:
> >> >>>
> >> >>>
> https://github.com/joyent/node/wiki/installing-node.js-via-package-manager
> >> >>>
> >> >>> https://github.com/saltstack-formulas/node-formula
> >> >>>
> >> >>>
> >> >>>
> https://docs.docker.com/installation/ubuntulinux/#ubuntu-precise-1204-lts-64-bit
> >> >>>
> >> >>> https://registry.hub.docker.com/u/jupyter/jupyterhub/
> >> >>>
> >> >>> On Feb 6, 2015 9:00 PM, "John Omernik" <john at omernik.com> wrote:
> >> >>>>
> >> >>>> In the Jupyter Hub, there's
> >> >>>>
> >> >>>> JupyterHub requires IPython >= 3.0 (current master) and Python >=
> >> >>>> 3.3.
> >> >>>>
> >> >>>> You will need nodejs/npm, which you can get from your package
> >> >>>> manager:
> >> >>>>
> >> >>>> sudo apt-get install npm nodejs-legacy
> >> >>>>
> >> >>>> (The nodejs-legacy package installs the node executable, which is
> >> >>>> required for npm to work on Debian/Ubuntu at this point)
> >> >>>>
> >> >>>> Then install javascript dependencies:
> >> >>>>
> >> >>>>
> >> >>>> However, I am running Ubuntu 12.04, and there is no nodejs-legacy.
> >> >>>> How do I meet that requirement?
> >> >>>>
> >> >>>> Thanks!
> >> >>>> _______________________________________________
> >> >>>> IPython-dev mailing list
> >> >>>> IPython-dev at scipy.org
> >> >>>> http://mail.scipy.org/mailman/listinfo/ipython-dev
> >> >>>
> >> >>>
> >> >>> _______________________________________________
> >> >>> IPython-dev mailing list
> >> >>> IPython-dev at scipy.org
> >> >>> http://mail.scipy.org/mailman/listinfo/ipython-dev
> >> >>>
> >> _______________________________________________
> >> IPython-dev mailing list
> >> IPython-dev at scipy.org
> >> http://mail.scipy.org/mailman/listinfo/ipython-dev
> >
> >
> >
> > _______________________________________________
> > IPython-dev mailing list
> > IPython-dev at scipy.org
> > http://mail.scipy.org/mailman/listinfo/ipython-dev
> >
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20150207/5c017f40/attachment.html>


More information about the IPython-dev mailing list