Distributions: Please add support for Ubuntu 19.10 (Eoan Ermine)

[rakanskiy]

Please consider to add upcoming Ubuntu release

[ghost]

Specially relevant now that it is officially released.

[christopherMills]

Really relevant.

[carlosSoto2]

extremely relevant

[pksasso]

Really important.

[Georgebillion]

extremely relevant

[AnnigilatorKM]

Please add support for Ubuntu 19.10, really important

[vadimfrolov]

Please add support for Ubuntu 19.10

[christian-ehmke]

Please add support for Ubuntu 19.10, really important.

[DevanshChoudaha]

Please add the support for Ubuntu 19.10 Eoan Ermine. We're are requiring node to build a back-end, and it's not being downloaded.

[Jav3k]

@Developer-Devansh, you can download latest version from https://nodejs.org/en/download/current/

or you can temporarily install nodejs snap package

snap install node --classic --channel=12

but snap is not recommended for production deployments

[imsmit]

I've installed nodejs using snap, & rest is working good for channel=10. But I'm getting EACCESS error for any command I pass with -g. "sudo npm install -g package-name" works neither.

[vohzd]

yep, builds are broken - please add support!

[sykeben]

I would love to continue developing with Node, too! I recently replaced Windows 10 with Ubuntu 19.10 and when it came time to reinstall nodejs, the Ubuntu CURL installer seemed to fail here:

## Confirming "eoan" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_12.x/dists/eoan/Release'

## Your distribution, identified as "eoan", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support

[creid58]

Please add support

[RAYs3T]

Please add support for eoan.

[DorkmasterFlek]

Voicing support for this.

[christopherMills]

nvm is the best way of installing node until this is fixed.

[SergioGlorias]

pls add
snap is bug (only problems)

[CodingVampyre]

Since it seems to take a bit longer, I also want to voice need of installing node 12 || 13!

[SergioGlorias]

the only wood I found to use node 12.x
without waiting for the repo to be updated

is to enter repo and download .deb normally

but the problem is that there is no automatic update

who wants the intalators deb
13.x: https://deb.nodesource.com/node_13.x/pool/main/n/nodejs/
12.x: https://deb.nodesource.com/node_12.x/pool/main/n/nodejs/
10.x: https://deb.nodesource.com/node_10.x/pool/main/n/nodejs/

edit:
I just entered the repository link through the site and found the installers .deb
which happens to be the same deb for all distros

[mortadda]

for now we can install its manually by another dist :

$  sudo apt-get install curl
$  curl -sSL https://deb.nodesource.com/gpgkey/nodesource.gpg.key | sudo apt-key add -

$  nano /etc/apt/sources.list.d/nodesource.list
# add this lines 
deb https://deb.nodesource.com/node_12.x disco main 
deb-src https://deb.nodesource.com/node_12.x disco main

$  sudo apt-get update
$  sudo apt-get install nodejs

now

$ nodejs -v
v12.13.0

[JungMinu]

Hi, we're in the middle of adding support for Ubuntu 19.10 and will keep you guys updated

[Congelli501]

Support for Ubuntu 19.10 / eoan is in place for 12.x & 13.x :confetti_ball:!
(I just saw the repo & install script were now working, i don't have any credit for it).

A proper nodesource team announcement will probably follow.

[JungMinu]

We've added support for Ubuntu 19.10 and thus closing this issue

[petercunha]

[jwatt]

@JungMinu The version number in the Description line in https://deb.nodesource.com/node_13.x/dists/eoan/Release is wrong. It says "for the Node.JS 12.x Branch" instead of "for the Node.JS 13.x Branch.

[jwatt]

In fact that seems to be the case for all Release files under that directory that I checked.

[khteh]

We've added support for Ubuntu 19.10 and thus closing this issue

Don't think so:

 $ curl -sL --insecure https://deb.nodesource.com/setup_13.x | sudo bash -
## Installing the NodeSource Node.js 13.x repo...


## Populating apt-get cache...

+ apt-get update
Get:1 http://packages.microsoft.com/repos/vscode stable InRelease [3,959 B]
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease                                                                                                                                
Hit:3 http://dl.google.com/linux/chrome/deb stable Release                                                                                               
Get:4 http://packages.microsoft.com/repos/vscode stable/main amd64 Packages [152 kB]                               
Hit:6 http://ppa.launchpad.net/linuxuprising/java/ubuntu eoan InRelease                                                                          
Hit:7 http://sg.archive.ubuntu.com/ubuntu eoan InRelease                                                          
Hit:8 http://archive.canonical.com/ubuntu eoan InRelease                                    
Hit:10 http://sg.archive.ubuntu.com/ubuntu eoan-updates InRelease     
Hit:11 http://sg.archive.ubuntu.com/ubuntu eoan-backports InRelease          
Hit:9 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Hit:12 http://security.ubuntu.com/ubuntu eoan-security InRelease
Fetched 156 kB in 6s (24.8 kB/s)                                                                                                                                                                                  
Reading package lists... Done

## Confirming "eoan" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_13.x/dists/eoan/Release'

## Your distribution, identified as "eoan", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support

[jwatt]

@khteh Note that it looks like eoan support was only added going back as far as node 10:

https://deb.nodesource.com/node_10.x/dists/eoan/Release

If you're trying to use an earlier node release you'd still expect to get that error message.