Streisand sets up a new server running your choice of WireGuard, OpenConnect, OpenSSH, OpenVPN, Shadowsocks, sslh, Stunnel, or a Tor bridge. It also generates custom instructions for all of these services. At the end of the run you are given an HTML file with instructions that can be shared with friends, family members, and fellow activists.
however, several packages requires pbr!=2.1.0,>=2.0.0
ERROR: oslo-i18n 3.25.1 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible.
ERROR: debtcollector 2.0.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible.
ERROR: oslo-utils 4.0.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible.
ERROR: oslo-serialization 3.0.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible.
ERROR: stevedore 1.31.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible.
ERROR: os-service-types 1.7.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible.
ERROR: keystoneauth1 3.18.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible.
ERROR: python-keystoneclient 3.22.0 has requirement pbr!=2.1.0,>=2.0.0, but you'll have pbr 1.10.0 which is incompatible.
after the last command, it warns build-essential python3-pip python3-dev python3-setuptools python-cffi libffi-dev libssl-dev libcurl4-openssl-dev are missing
following the installation instructions: https://github.com/StreisandEffect/streisand/blob/master/Installation.md
Expected behavior:
Install all the necessary packages without error
Actual Behavior:
when running
./util/venv-dependencies.sh ./venv
it installs pbr version 1.10.1
however, several packages requires pbr!=2.1.0,>=2.0.0
Steps to Reproduce:
Ubuntu 18.04 LTS, Nanode 1GB: 1 CPU, 25GB Storage, 1GB RAM
after the last command, it warns build-essential python3-pip python3-dev python3-setuptools python-cffi libffi-dev libssl-dev libcurl4-openssl-dev are missing
Also the same errors shows up when following the installation instructions on macOS 10.15.3 (19D76)
The main question is "can these errors be safely ignored?"