Added ursa to the core.ubuntu.dockerfile install

[pSchlarb]

Testpool started with the pool_start.sh script after the changes
Fixes #1624

Signed-off-by: Philipp Schlarb [email protected]

[sovbot]

Can one of the admins verify this patch?

[WadeBarnes]

(ci) test this please

[WadeBarnes]

I get the following errors when trying to build with this dockerfile:

#12 3.258 Some packages could not be installed. This may mean that you have
#12 3.258 requested an impossible situation or if you are using the unstable
#12 3.258 distribution that some required packages have not yet been created
#12 3.258 or been moved out of Incoming.
#12 3.258 The following information may help to resolve the situation:
#12 3.258
#12 3.258 The following packages have unmet dependencies:
#12 3.289  indy-node : Depends: indy-plenum (= 1.13.0.dev1034) but it is not going to be installed
#12 3.289              Depends: timeout-decorator (= 0.4.0) but it is not installable
#12 3.289              Depends: distro (= 1.3.0) but it is not installable
#12 3.295 E: Unable to correct problems, you have held broken packages.
#12 ERROR: executor failed running [/bin/sh -c apt-get update -y && apt-get install -y indy-node libindy ursa=0.3.2-2]: exit code: 100

[WadeBarnes]

The underlying issue in my case is this that the version of indy-node being installed is requiring indy-plenum==1.13.0.dev1034 then is should be requiring indy-plenum==1.13.0~dev1034. All versions of indy-node from version 1.13.0~dev1240 seem to be affected by this issue.

[WadeBarnes]

The issue was introduced here; 5bf71f4

and then fixed here; 6bd7f20

There is no package associated to the fix because the Jenkins builds have been failing to publish since October 14th.

I'd recommend switching over to the builds published via the GHA workflows.

# Hyperledger Repo Key
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 9692C00E657DDE61

echo "deb  https://hyperledger.jfrog.io/artifactory/indy xenial main"  >> /etc/apt/sources.list

[WadeBarnes]

The Jenkins CD builds have been partially stuck due to pip version dependencies which should be resolved with #1684.

[shashank-shekher]

The problem still persists to date. I got the following error while trying to build node with docker:

Step 8/13 : RUN echo "deb https://repo.sovrin.org/sdk/deb xenial master" >> /etc/apt/sources.list
 ---> Using cache
 ---> f70d55e90373
Step 9/13 : RUN useradd -ms /bin/bash -l -u $uid indy
 ---> Using cache
 ---> caa6b4b9e80f
Step 10/13 : RUN apt-get update -y && apt-get install -y indy-node libindy
 ---> Running in 5f344966b42c
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [99.8 kB]
Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [99.8 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [97.4 kB]
Get:5 https://repo.sovrin.org/deb xenial InRelease [28.4 kB]
Get:6 https://repo.sovrin.org/sdk/deb xenial InRelease [30.9 kB]
Get:7 https://repo.sovrin.org/deb xenial/master amd64 Packages [351 kB]
Get:8 https://repo.sovrin.org/sdk/deb xenial/master amd64 Packages [558 kB]
Fetched 1265 kB in 3s (378 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
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:
 indy-node : Depends: indy-plenum (= 1.13.0.dev1034) but it is not going to be installed
             Depends: timeout-decorator (= 0.4.0) but it is not installable
             Depends: distro (= 1.3.0) but it is not installable
E: Unable to correct problems, you have held broken packages.
The command '/bin/sh -c apt-get update -y && apt-get install -y indy-node libindy' returned a non-zero code: 100

@WadeBarnes Is there some workaround to this problem, esp. because this thread is 8 months old? Thanks in advance.

[cjhowland]

@pSchlarb Could you provide a brief update on this PR? With recent branch changes and the current development process on Indy Node/Plenum, we are wondering if these changes are still viable. If so, please close this PR and retarget it to main.

We will discuss and determine which PRs should be merged or closed at the next Indy Contributors Working Group meeting on May 9, 2023.

[pSchlarb]

I think I will encounter this issue during the testing for the new network from scratch documentation. And if persistent will fix it with that PR,if that is ok. Or should it be 2 separate prs @WadeBarnes?

[WadeBarnes]

@pSchlarb, One PR would be fine. I'd close this PR.