E: Unable to Locate Package Heroku-Toolbelt

E: Unable to locate package heroku-toolbelt

I suspect this issue may indeed be temporary, but if you need the heroku toolbelt installed now, you can install the standalone client instead of the ubuntu/debian bundle.

wget -qO- https://toolbelt.heroku.com/install.sh | sh

On an Ubuntu-based distro, however, the above will likely throw some errors:

sh: 7: [[: not found
sh: 29: [[: not found
Installation complete

This is because on Ubuntu systems /bin/sh is dash, not bash. You could either get the script and modify it to use bash instead of sh (sh is called within the script, just changing sh to bash in the command above won't suffice), or, you could ignore the errors and just do what the error-ing portion of the script instructs you to do:

Add the Heroku CLI to your PATH using:

echo 'PATH="/usr/local/heroku/bin:$PATH"' >> ~/.profile

You'll need to logout/login again to register the path addition, or just execute heroku directly in the mean time:

/usr/local/heroku/bin/heroku

Heroku not installing properly on Raspberry-Pi

Your question:

Is Heroku compatible with Raspbian?

Answer: Yes it is.


They currently working on a cross-platform install method for the CLI with snap. But folks have gotten the CLI to install on arm via npm but they don't officially support it. Snap should be a great solution for arm users when it's ready. But at the moment, you could install the standalone heroku toolbelt for linux arm like it is described in Standalone installation

# Run this from your terminal.
# Replace OS with one of “linux”, “darwin”, “windows”, “freebsd”, “openbsd”
# Replace ARCH with one of “amd64”, “386” or “arm”
wget https://cli-assets.heroku.com/branches/stable/heroku-OS-ARCH.tar.gz
mkdir -p /usr/local/lib /usr/local/bin
tar -xvzf heroku-OS-ARCH.tar.gz -C /usr/local/lib
ln -s /usr/local/lib/heroku/bin/heroku /usr/local/bin/heroku
# ensure that /usr/local/bin is in the PATH environment variable

Unable to install Heroku toolbelt in Ubuntu AWS instance

I think your sh is not a symlink to bash. Try

wget ...blah... | /bin/bash

and see if that helps.

--EDIT--

Ha! Would you believe it! Not 5 minutes after answering, I had the same problem. Here's the fix:

  1. Download the install.sh file
  2. Modify the line that says sudo sh to say sudo /bin/bash
  3. Run it with /bin/bash install.sh

The cause is that on some Ubuntu's, /bin/sh is actually a link to /bin/dash (not bash). And the install script uses some bash-isms without actually checking to see if you're using bash or not.



Related Topics



Leave a reply



Submit