Grails on Ubuntu 12.10 - grails

I am installing Grails on Ubuntu 12.10, using the instructions here, but an getting an error on the 3rd step, as outlines below.
sudo add-apt-repository ppa:groovy-dev/grails
sudo apt-get update
sudo apt-get install grails-ppa
The error I get is shown below. I have the Sun JDK installed, and JAVA_HOME is set, and JAVA_HOME/bin is on the path.
Can someone suggest things to try to resolve this?
/home/edgecase> $ sudo apt-get install grails-ppa
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:
default-jre-headless:i386 : Depends: openjdk-7-jre-headless:i386 (>= 7~u3-2.1) but it is not going to be installed
openjdk-7-jre:i386 : Depends: openjdk-7-jre-headless:i386 (= 7u7-2.3.2a-1ubuntu1) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
/home/edgecase> $ java -version
java version "1.6.0_39"
Java(TM) SE Runtime Environment (build 1.6.0_39-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01, mixed mode)

We need to remove those instructions from the site since the PPA isn't being maintained. Use http://gvmtool.net/ instead.

YES please remove the PPA instructions with GVM, I wasted a lot of time before I found this

Related

Installing Specific Docker Version via Puppet

While deploying docker using puppet, I encounter an interesting issue.
docker installs fine if I use: version => latest
docker install fails if I use: version => '20.10.16'
My setup is as follows:
puppet master is Ubuntu 20.04.
puppet agent is Ubuntu 22.04 (on which I am trying to install docker).
I believe puppet docker module supports this setup.
The version lines I tried:
version => '20.10.16'
version => '20.10.16~3-0~ubuntu'
version => '20.10.16~3-0~ubuntu-jammy'
The error I get when I specify a specific version is as follows:
Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install docker-ce=20.10.16' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Package docker-ce is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
docker-ce-cli
Anyone has any idea what can be done so that it installs specific version of docker instead of the latest one?
When running apt-cache madison docker-ce it appears that the version number is 5:20.10.16~3-0~ubuntu-jammy.
Running apt install docker-ce=20.10.16~3-0~ubuntu-jammy returns the same error as yours, but apt install docker-ce=5:20.10.16~3-0~ubuntu-jammy works.
I suggest trying with the 5: in front of the version number.

python3-wheel installed, still using legacy 'setup.py' when installing dlib

I've forked dlandon's Zoneminder project in order to build a Docker image using Debian Bullseye instead of Ubuntu, for i386 (I'm installing it into a 32-bit mini PC).
Part of the requiriments is installing dlib (latest is 19.22.0). I've installed the required dependencies (python3-pip, python3-setuptools and python3-wheel, as well as GCC and CMake).
When installing dlib, the terminal outputs:
Collecting dlib
Downloading dlib-19.22.0.tar.gz (7.4 MB)
Using legacy 'setup.py install' for dlib, since package 'wheel' is not installed.
Installing collected packages: dlib
Running setup.py install for dlib: started
...
The relevant part is (even with python3-wheel installed)
Using legacy 'setup.py install' for dlib, since package 'wheel' is not installed.
dlib builts successfully but takes a looong time to build, however. This happens with any packages supossed to use wheel.
I haven't found any (answered) questions about this specific issue, so, if there is something I missed, I would be told about that.
Everything is in the Dockerfile.
try pip install wheel in your env

Erlang and epmd installation from binary has circular dependency

Pardon my English.
I am trying to install Erlang 23 on a SUSE Linux Enterprise Server Version 12 Patch 3 which is not connected to Internet so I cannot use zypper or wget and have to install it manually using binary.
I get the below errors :
erlang-epmd is needed by erlang-23.0.2-1.2.x86_64 when installing erlang.
erlang = 23.0.2 is needed by erlang-epmd-23.0.2-1.2.x86_64 when installing erlang-empd.
How to resolve this circular dependency?
You can install codependent RPMs by putting them together in the same command, e.g.:
rpm -iv erlang-23.0.2-1.2.x86_64.rpm erlang-epmd-23.0.2-1.2.x86_64.rpm

How to setup ROS environment variable on Ubuntu 20.04?

I tried following this guide to install ROS, but even after adding ROS source.list and its key
sudo apt install ros-melodic-desktop-full
gave error.
E: Unable to locate package ros-melodic-desktop-full
Then I ran this command
sudo apt search ros
to see if any such package exists. I couldn't find ros-melodic-desktop-full but I found another similar package ros-desktop-full.
So I installed it instead. The installation went smooth without giving any errors.
Next step in the guide is to set-up ROS environment variable, but I have no such directory
/opt/ros
So how do I setup the environment variable?
P.S.
I also installed some tools and dependencies with this command
sudo apt install python3-rosdep python3-rosinstall python3-rosinstall-generator python3-wstool build-essential
and initialized rosdep
sudo rosdep init
rosdep update
The ros-desktop-full package you installed is part of the official Ubuntu release.
ROS Melodic (and in the future, Noetic) is published by the OSRF in a separate repository (packages.ros.org). These packages install to /opt/ros/. However, some ROS packages have also been ported to Debian, which is how they found their way to Ubuntu (which derives from Debian).
The Debian packages are fully functional, but they do not install to /opt/ros. Instead, everything is integrated in the operating system itself. This means that you need to set up your personal workspace slightly differently.
Given that most tutorials assume that you use the OSRF packages, I suggest you either wait for the Noetic release (scheduled for the end of May 2020), then install ros-noetic-desktop-full, or downgrade to Ubuntu 18.04 LTS to use ROS Melodic.
From the documentation here, melodic is only supported on Ubuntu 18.04. The ROS version targeting Focal (20.04) is Noetic, but that one has not been released yet (see Distributions). I'm not sure what ROS version Ubuntu packages (the ros-desktop-full one you installed), but I was not successful in using it.
If you really do want to use Ubuntu 20.04, then I think your best option currently is to compile from source. Last time I checked the precompiled debs for Noetic are not yet available at http://packages.ros.org/ros/ubuntu (you can track release progress at github issue 21513). No idea if compiling Noetic from source is easy or hard, but I was able to compile ROS2 foxy from source without too much trouble though.

Cypher shell not installable (Ubuntu 16.04)

On Ubuntu 16.04, I've added the package repo for Neo4j (http://debian.neo4j.org/), but when I try to do sudo apt-get upgrade neo4j I get:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... 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:
neo4j : Depends: cypher-shell but it is not installable
E: Broken packages
I've tried to find the package repo where cypher-shell resides, but to no avail. Where is it?
Thanks for reporting this. We have now released cypher-shell to the repo and Neo4j 3.1.4 installs successfully.

Resources