Trying to install Docker in Ubuntu trusty following instructions here:
https://docs.docker.com/engine/installation/linux/docker-ce/ubuntu/
Tried first to use repo. That failed with
E: Unable to locate package docker-ce
Next, tried to download .deb file, but I could not find it at
https://download.docker.com/linux/ubuntu/dists/trusty/stable/
Finally tried get-docker.sh script, that failed with:
W: Failed to fetch https://download.docker.com/linux/ubuntu/dists/trusty/InRelease Unable to find expected entry ‘edge/binary-i386/Packages’ in Release file (Wrong sources.list entry or malformed file)
How can I do this install? This should not be so hard, so it’s probably me, but I don’t know what I am doing wrong.
Related
I am running the demo MoveIt Servoing,I am using the following commands
1. roslaunch ur_gazebo ur5.launch
2. roslaunch ur5_moveit_config ur5_moveit_planning_execution.launch sim:=true
3. roslaunch ur5_moveit_config moveit_rviz.launch config:=true
After running the following command
4. roslaunch moveit_servo spacenav_cpp.launch
I am getting the following error Could not open the space navigator device. Did you remember to run spacenavd (as root)? I tried resolving the issue using the [website Link Solution], however I am getting the following error
root#abc-ThinkPad-P17-Gen-2i:/home/abc/ws_moveit# rosrun spacenav spacenavd
Command 'rosrun' not found, but can be installed with:
apt install rosbash
root#abc-ThinkPad-P17-Gen-2i:/home/abc/ws_moveit# sudo apt install rosbash
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
rosbash : Depends: catkin but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root#abc-ThinkPad-P17-Gen-2i:/home/abc/ws_moveit#
I am using Ubuntu 20.04 and ROS Noetic
Okay. I will also post this on stackoverflow and update here if I found I solution there.
I am currently trying to install Drake's binary installation for python (note I am downloading the bionic release for Ubuntu). I am following the instructions found here: https://drake.mit.edu/python_bindings.html#inside-virtualenv I have noticed once I run:
<venv_path>/share/drake/setup/install_prereqs
I receive the following error that states that it cannot find the bionic release.:
Notice err 8 that states Err:8 http://ppa.launchpad.net/zedtux/naturalscrolling/ubuntu bionic Release
404 Not Found [IP: 91.189.95.85 80]
I believe this is why is subsequently cannot import pydrake. Has anyone run into this issue before? Do you have any suggestions as to why this may be the case?
I think that if you run "sudo apt update" on the command line, you'll see the same error. If so, your problem is not related to Drake. The Ubuntu installation itself is broken, because it is configured to use PPA that no longer exists.
You should disable or remove that PPA; perhaps https://askubuntu.com/questions/307/how-can-ppas-be-removed is useful, or else just search "remove ubuntu ppa" and there are several suggestions.
I'm trying to download docker on my raspberry pi 4 but I keep getting the same error.
The error message I get is:
W: https://deb.nodesource.com/node_14.x/dists/buster/InRelease: No system certificates available. Try installing ca-certificates.
W: https://deb.nodesource.com/node_14.x/dists/buster/Release: No system certificates available. Try installing ca-certificates.
E: The repository 'https://deb.nodesource.com/node_14.x buster Release' no longer has a Release file.
I don't understand this because I've re-installed ca-certificate but that still doesn't fix it.
(Note: I don't know if this means anything but I also get the same error when I run sudo apt update)
Okay I fixed the problem by simple running sudo apt-get install --reinstall ca-certificates
Being in China means sometimes you just can't upgrade brew packages via brew upgrade it would run into error as such:
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to cli-assets.heroku.com:443
Error: An exception occurred within a child process:
DownloadError: Failed to download resource "heroku"
Download failed: https://cli-assets.heroku.com/heroku-v7.18.10/heroku-v7.18.10.tar.xz
I used to download these failed packages to ~/Library/Caches/Homebrew and then run the command again but this seems to work no longer after brew changed its cache structure for the better or worse (worse for me apparently).
What can I do now if I want to keep using brew to upgrade all my packages?
After I tried your method, this is the error that pops up:
==> Upgrading heroku/brew/heroku
==> Installing dependencies for heroku/brew/heroku: heroku/brew/heroku-node
==> Installing heroku/brew/heroku dependency: heroku/brew/heroku-node
==> Downloading https://cli-assets.heroku.com/homebrew/node-11.3.0.tar.xz
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to cli-assets.heroku.com:443
Error: An exception occurred within a child process:
DownloadError: Failed to download resource "heroku-node"
Download failed: https://cli-assets.heroku.com/homebrew/node-11.3.0.tar.xz
Also, say if I download go from https://dl.google.com/go/go1.11.4.src.tar.gz and rename it to go--git, which is the output of brew --cache go, but it still failed the installation.
fatal: unable to access 'https://go.googlesource.com/tools.git/': Failed to connect to go.googlesource.com port 443: Operation timed out
Error: An exception occurred within a child process:
DownloadError: Failed to download resource "go--gotools"
Failure while executing; `git clone --branch release-branch.go1.11 https://go.googlesource.com/tools.git /Users/aero/Library/Caches/Homebrew/go--gotools--git` exited with 128. Here's the output:
Cloning into '/Users/aero/Library/Caches/Homebrew/go--gotools--git'...
fatal: unable to access 'https://go.googlesource.com/tools.git/': Failed to connect to go.googlesource.com port 443: Operation timed out
If I run brew --cache go--gotools, it will say Error: No available formula with the name "go--gotools"
If, for example, you want to upgrade Gradle, you can find the location and the name of the cached file expected by Homebrew with:
brew --cache gradle
You will obtain:
/Users/myself/Library/Caches/Homebrew/downloads/ae76f5a0a19f5c141d5ee602a2ecb45011393fbba2206f3a960599d7bba92b9b--gradle-5.0-all.zip
Extract the url of the zip file from:
brew edit gradle
Download the file and rename it as in the output of brew --cache
You can then upgrade Gradle even offline with:
brew upgrade gradle
Depending on formulas, you will have to manually install all their dependencies.
If you use the -v option of brew upgrade or brew install or whichever command you used that needs to download the file, it will give you the output file where the downloaded file would have gone. You can then download your file manually to this place.
I'm unable to install dse-full or opscenter due to the following transaction errors
Total
Running transaction check
Running transaction test
Transaction check error:
file /usr/bin from install of dse-libcassandra-3.1.4-1.noarch conflicts with file from package filesystem-3.2-13.fc19.x86_64
file /usr/sbin from install of dse-libcassandra-3.1.4-1.noarch conflicts with file from package filesystem-3.2-13.fc19.x86_64
Error Summary
-------------
Is there some yum foo to get around this? Why would the package include a /user/bin and /usr/sbin?
**UPDATE Resolved**
I was able to work around this by doing the following:
Downloaded the latest rpm from the datastax repository using my login credentials:
wget http://xxx:xxx#rpm.datastax.com/enterprise/noarch/dse-libcassandra-3.1.4-1.noarch.rpm
Then ran:
rpm -Uvh --force dse-libcassandra-3.1.4-1.noarch.rpm
I had to do the same thing to get opscenter installed. I believe the rpm's were packaged incorrectly and hope it is resolved in a future release.
**NOTE**
If you use this solution you should also download the filesystem rpm and run:
rpm -Uvh --force filesystem-3.2-13.fc19.x86_64.rpm
This way /usr/bin and /usr/sbin is owned by the filesystem package again. Otherwise you might run into problems later trying to upgrade fedora.
Yes this is an issue in the rpm spec that has been resolved for upcoming releases. Both packages erroneously try to take control over /usr/bin and /usr/sbin.