Cli: Unable to install heroku cli on ubuntu 18.04

Created on 5 May 2018 · 5Comments · Source: heroku/cli

On ubuntu 18.04 I tried several ways of installation.

App center will not provide any extra error information but will state "Unable to install heroku"

Snap produces the following error:

sudo snap install heroku --classic
error: cannot perform the following tasks:
- Run configure hook of "heroku" snap if present (run hook "configure": /snap/heroku/2434/snap/hooks/configure: 3: /snap/heroku/2434/snap/hooks/configure: heroku: not found)

Also when trying to install standalone, error related to gpg keys occurs (which was already reported a year ago)

W: GPG error: https://cli-assets.heroku.com/branches/stable/apt ./ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C927EBE00F1B0520
E: The repository 'https://cli-assets.heroku.com/branches/stable/apt ./ InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Any ideas? This is a clean ubuntu install, but I noticed the same issue on an elementaryOS Loki 0.4 (i think) box as well.

Source

sf-jd

Most helpful comment

I've fixed the issue with snap. I'm not sure what App Center even is. If it's using the snap under the hood it should work now.

Did you run the apt script? curl https://cli-assets.heroku.com/install-ubuntu.sh | sh it should add the key automatically.

jdxcode on 5 May 2018

👍11

All 5 comments

I've fixed the issue with snap. I'm not sure what App Center even is. If it's using the snap under the hood it should work now.

Did you run the apt script? curl https://cli-assets.heroku.com/install-ubuntu.sh | sh it should add the key automatically.

jdxcode on 5 May 2018

👍11

App Center == Ubuntu software
I believe it uses snap as i was able to install through there and which heroku => /snap/bin/heroku

Regarding the apt script, that's where im getting the actual GPG error listed above. Happened again just now when running it.

woops, edit: Thanks for taking care if the issue!

sf-jd on 5 May 2018

the script doesn't use the "branches" path anymore so it must be old I think. Check your sources to see if you've got an old Heroku reference somewhere. Let me know where you find it too so I can have the script clean that up automatically

jdxcode on 5 May 2018

This also worked for me whilst in the middle of installing Mongodb during the get update version. For anyone wondering the error reads as followed. I am currently running Ubuntu v17.10

E: Repository 'https://cli-assets.heroku.com/branches/stable/apt ./ InRelease' changed its 'Origin' value from 'Heroku, Inc.' to 'Heroku'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Hope this helps. GF all!

MacusDesir on 30 Jun 2018

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 Release: The following signatures were invalid: KEYEXPIRED 1507497109
W: Failed to fetch http://repo.mongodb.org/apt/ubuntu/dists/xenial/mongodb-org/3.2/Release.gpg The following signatures were invalid: KEYEXPIRED 1507497109
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/restricted/dep11/Components-amd64.yml Could not open file /var/lib/apt/lists/partial/security.ubuntu.com_ubuntu_dists_xenial-security_restricted_dep11_Components-amd64.yml.gz - open (13: Permission denied) [IP: 91.189.88.149 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

on ubuntu 16.04
please help