typedb: Installing Grakn via APT fails because it depends on an older version of a dependency binary

Description

The version 2.0.0-alpha-2 cannot be installed via APT.

Environment

  1. OS: Ubuntu 20.04 server
  2. Grakn version (and platform): 2.0.0-alpha-2
  3. Grakn client: N.A.
  4. Other environment details:

Reproducible Steps

$ sudo apt-get install grakn-core-all
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:
 grakn-core-all : Depends: grakn-core-server (= 2.0.0-alpha-2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
$ sudo apt-get install grakn-core-server
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:
 grakn-core-server : Depends: grakn-bin (= 2.0.0-alpha-5) but 2.0.0-alpha-6 is to be installed
E: Unable to correct problems, you have held broken packages.

Expected Output

Software installs.

Actual Output

Software does not.

Additional information

The problem lies in the debian/control file for grakn-core-server that states = 2.0.0-alpha-5 instead of >= 2.0.0-alpha-5

About this issue

  • Original URL
  • State: open
  • Created 6 years ago
  • Reactions: 1
  • Comments: 21 (9 by maintainers)

Most upvoted comments

NOTE: The issue that you have experienced only occurs if you happen to install while the Vaticle team is in the middle of releasing a new version (which may take several hours). Otherwise, APT installation should work just fine.

When you do experience the issue however, the workaround is by specifying the exact version of each package, outlined below.

First, let’s start off clean and remove the distribution completely:

apt remove grakn-core-all grakn-core-server grakn-console grakn-bin

Then, let’s reattempt the installation, making sure to specify the exact version of each package:

apt install grakn-core-all=2.0.1 grakn-core-server=2.0.1 grakn-console=2.0.0 grakn-bin=2.0.0

This is not the ideal state of things and we are trying to find out how to configure APT properly, to avoid issues like this one. If any of you guys can spot the errors in how we declare the APT package a PR would be more than welcome.

Forgot to mention if someone reads that, but you can solve the issue with : $ sudo apt-get install grakn-bin=2.0.0-alpha-5 and then install the software 😉