I maintain a small group of linux machines, all with Xubuntu 14.04 on them. I recently worked out a way (with help from Martin and Markus) to be able to have the previous devel version of GRASS 70 installable via the ppa repositories “grass-devel” and “ubuntugis-unstable”, which worked well and let me maintain current grass7 installs on all my machines, alongside grass6 stable. This has changed with the release of grass7 stable, which I’m trying to upgrade to on all the machines. What happens is that the ubuntu package manager will not let me have BOTH grass7 stable AND grass6 stable installed at the same time. I have a feeling that the package manager believes there to be some conflict, although there should be none. Does anyone have an idea as to what may be causing this, and how it can be fixed? I’m happy to help in any way that I can, but repo packaging is not something I know a huge amount about.
Oh, and to add just an extra “twist”, I’m able to install the grass 7 “daily” package along side either grass7 or grass6. It seems just that the two stable releases cannot live together (at least according to the package manager)…
Cheers,
···
Isaac I Ullah, Ph.D.
Arizona State University
School of Human Evolution and Social Change
PO Box 2402
Tempe, AZ 85287-2402
(480) 727-1054 office
(650) 201-0479 cell iullah@asu.edu
I have a feeling that the package
manager believes there to be some conflict, although there should be none.
Does anyone have an idea as to what may be causing this, and how it can be
fixed?
The cause is the recent addition of conflicts with the official Debian
package for grass, see:
These Conflicts need to be removed from the GRASS upstream packages to
allow co-installation of grass & grass7.
does it mean to remove Conflicts from rules file on Launchpad or?
Yes, you need to remove the Conflicts from the GRASS packaging on
Launchpad to fix this issue.
While you're at it, there are some fixes you need in
grass7-core.links & grass7-core.links.in:
- remove the symlink from grass70 to itself,
the symlink from grass to grass70 was a cause of conflicts between
the grass & grass70 packages.
- remove the symlink from grass@VERSION@.1.gz to grass.1.gz,
grass7-core.links is correct, but grass7-core.links.in is not.
The man pages in grass7-doc.install{,.in} is still a cause of conflict
between the grass & grass7 packages. Instead of use Conflicts to prevent
co-installation with dependencies, using the alternatives system to
switch between version like openjdk-6 & 7 uses is probably better.
While you're at it, there are some fixes you need in
grass7-core.links & grass7-core.links.in:
- remove the symlink from grass70 to itself,
the symlink from grass to grass70 was a cause of conflicts between
the grass & grass70 packages.
- remove the symlink from grass@VERSION@.1.gz to grass.1.gz,
grass7-core.links is correct, but grass7-core.links.in is not.
I fixed these issues and put to Launchpad the new packages as
`7.0.0-7`. Testing welcomed (the new package should be available in
30min).
The man pages in grass7-doc.install{,.in} is still a cause of conflict
between the grass & grass7 packages. Instead of use Conflicts to prevent
co-installation with dependencies, using the alternatives system to
switch between version like openjdk-6 & 7 uses is probably better.
If it's not already the plan to make the changes necessary to have
the new grass 7.0 alongside the official ubuntu grass6.4, then it
probably ought to be. Apologies if this is already in the works!
Apology accepted, because that's what the "grass70 package name" thread
I linked to is about.
The intention is to allow co-installation, but also preventing conflicts
between the official Debian package and those from the GRASS PPA.
The Conflicts change I proposed prevents some conflicts between the
official Debian package and the GRASS PPA, but prevents co-installation
as you have experienced.
The /usr/bin/grass & /usr/bin/x-grass symlinks in grass-core are not a
problem anymore, but there is still any issue with the man pages as I
wrote earlier in this thread.