Running indy-pool.dockerfile fails in Plenum Python package about indy-sdk HOT 6 CLOSED

this is an issue that appears due to the base58 version. It was recently updated and we chose to freeze the version we we're using and will update later. For now, if you run sudo pip install base58==0.2.5 then you the problem should be resolved.

from indy-sdk.

So although I pinned (or froze) every version of every possible indy package (e.g. libindy, indy-plenum, anoncreds, etc. as specified in the indy-pool.dockerfile), still the latest versions of python packages are pulled? Shouldn't those be pinned as well within the ubuntu packages of e.g. indy-plenum?

My point is: For development, I would like to have a stable version that does not change, which is why I pinned all the versions. However, this issue shows that somewhere within the ubuntu packages, the python packages are not versioned and the latest versions are pulled. This makes it incredibly inconvenient to develop for Indy since one day to the next (most often just before a demo of course), everything breaks. Can you not pin the python packages as well, when you make a new release?

from indy-sdk.

As i know team that supports Indy Node already solved this.

from indy-sdk.

@vimmerru can you link to an Issue or file where they fix this? I'm having another issue because of this as well and am blocked until this is resolved.

from indy-sdk.

@PJUllrich https://jira.hyperledger.org/browse/INDY-1287

from indy-sdk.

Thank you. We fixed this by pinning the base58 package ourselves by pinning the base58 package in the apt-get update command.
Note the added python3-base58=0.2.4 \ command.

RUN apt-get update -y && apt-get install -y \
        indy-plenum=${indy_plenum_ver} \
        indy-anoncreds=${indy_anoncreds_ver} \
        indy-node=${indy_node_ver} \
        python3-indy-crypto=${python3_indy_crypto_ver} \
        libindy-crypto=${indy_crypto_ver} \
        python3-base58=0.2.4 \
        vim

from indy-sdk.