-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
NodeJS 8.5.0 RPM package requires Python 2.6 #526
Comments
Python 2.x should always have been a dependency, it was an error if it wasn't in the past. The reason is that |
@chrislea I understand that Python is a dependency. When installing NodeJS 8.5 it correctly mentions that it needs Python > 2.6. The problem is however that Python 2.7 is already installed, yet it still installs 2.6. This didn't happen before with NodeJS 8.4. Steps to reproduce:
With NodeJS 8.5, I would also expect it not to install Python 2.6. |
Ah, sorry, misread your initial comment. We'll look into this. |
The problem is that the package AWS installs isn't called
We'll see if this is a thing we can work around. |
Unfortunately it doesn't look like this is a thing we can fix.
until version 4.13, which is newer than the version of The good news is that AWS Linux uses the alternatives system to choose what binary the Sorry we can't have a nicer fix, but outside of a bit of extra disk space used, this shouldn't have any negative effects on your system.
|
Hi @chrislea , thanks for looking into this! I'm curious though why it worked on NodeJS 8.4 and not on 8.5. Any idea? |
We (incorrectly) only had python as a build requirement and not an installation requirement prior to 8.5.0. This never got us in trouble, I suspect because RedHat / Fedora write all their system tools in python so it's always there, but it was still wrong. If the AWS folks fix their |
Everything clear now - thanks! I'll contact AWS to see if this can be resolved. |
I just ran into this on Debian, slightly different scenario... I'm running on an armhf device. I pre-build and package my entire application, including I've been using nodesource distributions of nodejs v4, v6 and v8.2 happily up to now with this setup. Then, as OP mentioned, between 8.4 and 8.5, I understand why, but realistically So now my options are:
|
The
On a ~400MB disk image this is not insignificant |
@thom-nic I think you're overlooking what's probably the easiest option in your case, which is simply to grab the binary tarball you want from https://nodejs.org/dist. That way you'd be getting the exact same bits we ship, but without any packaging dependencies. |
I had considered that. Is the install script doing more than untar to |
That is a helpful suggestion though. Before today I did not realize nodejs.org had an official armhf build. I've been using nodesource repos for quite some time since they used to be the only resource for prebuilt nodejs for ARM if I'm not mistaken. Thanks Chris! |
@thom-nic There have been both |
and move downloaded package to /tmp so as to delete it at the end. Install python-minimal which is required by NodeSource Node.js since 8.5.0, see nodesource/distributions#526
and move downloaded package to /tmp so as to delete it at the end. Install python-minimal which is required by NodeSource Node.js since 8.5.0, see nodesource/distributions#526
Since v8.5.0, when installing NodeJS on the Amazon Linux OS using the RPM it will also install Python 2.6 even if Python 2.7 is already installed.
This did not happen on NodeJS v8.4.0 so I believe something has changed in the specfile for the latest NodeJS version.
Is this something that can be fixed?
The text was updated successfully, but these errors were encountered: