I am trying to install the Heroku Toolbelt on Linux Mint 15 Olivia (x86-64)
When i try to run the standard command for installing on Debian machines:
wget -qO- https://toolbelt.heroku.com/install-ubuntu.sh | sh
I get:
W: Failed to fetch http://toolbelt.heroku.com/ubuntu/./Packages 302 Moved Temporarily [IP: 23.21.198.2 80]
...
E: Unable to locate package heroku-toolbelt
I have also got the heroku.list repo in my etc/apt/sources/:
deb http://toolbelt.heroku.com/ubuntu ./
When i try to add the repo again with:
sudo apt-add-repository 'deb http://toolbelt.herokuapp.com/ubuntu ./'
I get:
Cannot add PPA: 'No JSON object could be decoded'.
And it seems i'm not the first person with this error on Mint 15 while trying to add repositories.
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
Related
I have a strange problem with podman. I have a large Dockerfile of an open source project called spilo that I was always able to build. Today for some strange reason the same code doesn't work anymore. It's true that I haven't used podman for a month but today I got a strange problem. To simplify the error I created a simple Dockerfile just to show you the problem:
ARG BASE_IMAGE=ubuntu:18.04
ARG PGVERSION=14
ARG COMPRESS=false
FROM $BASE_IMAGE as builder-false
RUN apt-get update; apt-get install -y pgbackrest
FROM scratch as builder-true
COPY --from=builder-false / /
FROM builder-${COMPRESS}
Now if I run:
podman build . -t prova:latest
I got the following error:
[3/3] STEP 1/1: FROM builder-false
Resolving "builder-false" using unqualified-search registries (/etc/containers/registries.conf.d/999-podman-machine.conf)
Trying to pull docker.io/library/builder-false:latest...
Error: error creating build container: initializing source docker://builder-false:latest: reading manifest latest in docker.io/library/builder-false: errors:
denied: requested access to the resource is denied
unauthorized: authentication required
It seems it try to search the builder-false image from docker.io repository instead try to build it from the row above. The steps to create the builder-false are not executed.
Can anyone help me to address this issue?
The original spilo project Dockerfile always worked. I reinstalled the podman VM but no luck. I also restarted the Mac, no luck.
I think there is a bug somewhere in dependencies of pgbackrest. I got this on my podman (centos 8) executing RUN apt-get install -y pgbackrest:
chfn: PAM: System error
adduser: `/usr/bin/chfn -f PostgreSQL administrator postgres' returned error code 1. Exiting.
dpkg: error processing package postgresql-common (--configure):
installed postgresql-common package post-installation script subprocess returned error exit status 1
With docker works fine.
When i write [sudo apt-get update]
First error : https://pkg.jenkins.io/debian-stable binary/ Packages
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Second error : W: The repository 'http://pkg.jenkins.io/debian-stable binary/ Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://pkg.jenkins.io/debian-stable/binary/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Some index files failed to download. They have been ignored, or old ones used instead.
Try adding a '[trusted=yes]' tag in your /etc/apt/sources.list (or sources.list.d/file) file at the line related to http://pkg.jenkins.io/debian-stable...
At the end, in your souces.list file, you should end up with something like the following:
deb [trusted=yes] http://pkg.jenkins.io/.....
EDIT: this shell command should do the trick:
sed -i 's/^deb /deb [trusted=yes] /' /etc/apt/sources.list
then reload your apt cache with:
apt update
Hope it helps.
Follow Jenkins Debian Packages for all the commands to install Jenkins in Ubuntu.
Install Java
Update your local package index
sudo apt-get install jenkins
I have installed it on Ubuntu 22.04.1 LTS and created a Video Tutorial of it.
I'm following this link to install elixir and erlang on fedora 21... After i installed when i tried to run interactive elixir(iex) i get the following error
/home/hari/.asdf/installs/elixir/1.4.2/bin/elixir: line 126: exec: erl: not found
Commands i used to install :
asdf install erlang 19.0
asdf install elixir 1.3.2
But if i run as a root user its working correctly!!! What's the mistake im commiting here?
It’s a path issue. Please do the following to detect the problem root:
sudo su -c 'which erl'
#⇒ /usr/local/bin/erl # OR LIKE
It seems that this directory is not on your user’s path. Add it to test:
export PATH=`dirname $(sudo su -c 'which erl')`:$PATH
Try running elixir (it should succeed.) Now just put the hardcoded path in the very end of your shell start script (~/.bashrc if you use bash, etc):
export PATH=/usr/local/bin:$PATH
i'm trying to get jenkins running on debian 7 but i keep getting this error while apt-get install jenkins is running.
Setting up dbus (1.6.8-1) ...
Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[ ok ] Starting system message bus: dbus.
Also i get the message that jenkins is started at the end and no error message:
[ ok ] Starting Jenkins Continuous Integration Server: jenkins.
but /etc/init.d/jenkins status gives me the output that jenkins is not running. also ls -alh /var/lib/jenkins gives me an empty folder.
So the install fails with no error.
This is the way i'm running the install:
wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | apt-key add -
sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
apt-get update
apt-get install jenkins
Has anyone of you tried installing jenkins on a fresh debian 7?
looking forward for helping answers.
kind regards and thanks in advance
So i solved the problem finally.
I expected the Java SDK to have the right JRE in it, so i downloaded it from the Oracle website: jdk1.7.0_21-x64-linux.tar.gz after installing and registering this to my machine it worked java -version and javac -version.
Problem was the version of this JRE did not work with Jenkins so thanks to #wako, i installed openjdk-7-jre and i have now two jre's running on my machine but jenkins started finally. need to figure out if openjdk-7-jre suits my plans or if i need to fall back to Debian 6.
This is an issue with apt-get and not with Jenkins -
please make sure you run it as root.
Can try to install (or upgrade) another package, to confirm.
I had the same problem on the debian 7 freshly installed, via the light version of debian 7 with the ssh server only installed.
First I add the repository as you specified it, try to install jenkins but some dependencies were broken (daemon-psmisc-java2-runtime).
To solve the problem I did an:
apt-get -f upgrade
And it was OK
To complete the installation of jenkins you will need apache2 and java-jre
apt-get install apache2 openjdk-7-jre
I have finished installing RabbitMQ using the following RPM
http://www.rabbitmq.com/releases/rabbitmq-server/v2.7.1/rabbitmq-server-2.7.1-1.noarch.rpm
i installed it like so :
$ wget \ http://www.rabbitmq.com/releases/rabbitmq-server/v2.7.1/rabbitmq-server-2.7.1-1.noarch.rpm
$ rpm --nodeps -Uvh rabbitmq-server-2.7.1-1.noarch.rpm
the reason i used --nodeps was because i installed erlang from source and the rpm will try looking for an erlang.rpm dependency ignoring the one on the system.
When i try to start the Rabbit MQ server i get this error :
/usr/lib/rabbitmq/bin/rabbitmq-server: line 73: /var/lib/rabbitmq/mnesia/rabbit#
vz129.pid: Permission denied
{"init terminating in do_boot",{undef,[{rabbit_prelaunch,start,[]},{init,start_i
t,1},{init,start_em,1}]}}
Im using CentOS release 4.9 (Final).
Any help is appreciated.
It seems like it was a permissions error. all i did was run :
chown -R rabbitmq:rabbitmq /var/lib/rabbitmq/
and it worked :D