Install fails on debian bullseye

[RichieHH]

./install.sh

aketlisten werden gelesen… Fertig
+ echo
+ grep '3\.'
+ sudo apt-get -y install libreadline6-dev python-dev python-setuptools python-yaml python-pip
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Hinweis: »libreadline-dev« wird an Stelle von »libreadline6-dev« gewählt.
Hinweis: »python-dev-is-python2« wird an Stelle von »python-dev« gewählt.
Paket python-pip ist nicht verfügbar, wird aber von einem anderen Paket
referenziert. Das kann heißen, dass das Paket fehlt, dass es abgelöst
wurde oder nur aus einer anderen Quelle verfügbar ist.
Doch die folgenden Pakete ersetzen es:
  python3-pip

E: Paket python-yaml kann nicht gefunden werden.
E: Für Paket »python-pip« existiert kein Installationskandidat.

[Daniel Hahler]

Code ref:

voltron/install.sh

Lines 111 to 115 in d9fef0b

 if echo $PYVER|grep "3\."; then 
     sudo apt-get -y install libreadline6-dev python3-dev python3-setuptools python3-yaml python3-pip 
 else 
     sudo apt-get -y install libreadline6-dev python-dev python-setuptools python-yaml python-pip 
 fi 

Should probably fail with PYVER=2 (via python being a Python 2.x, or use/try python3 instead).

Not really a problem with voltron, but only its install.sh script.

[RichieHH]

Not really a problem with voltron, but only its install.sh script.

Erm, yes. ;) I installed it from Debian Bullseye repos, and there are issues too (it simply fell over starting up with a backtrace) but I didn't have time to follow them up - I'll look into that later and report back if I don't get it working,

[RichieHH]

Not really a problem with voltron, but only its install.sh script.

Erm, yes. ;) I installed it from Debian Bullseye repos, and there are issues too (it simply fell over starting up with a backtrace) but I didn't have time to follow them up - I'll look into that later and report back if I don't get it working,

OK, I had another look and it doesn't work from Debian 11 install either. An "async=True" problem and WerkZeug versioning issues : both referenced in other bug reports. Much as I'd like to use it, I don't have the time currently to mess around with python as I don't know anything about it. I did follow a PR to modify "async=True" to "asynchronous = True" in memory.py but I couldn't get any voltron views to connect despite ensuring entry.py was sourced and "voltron loaded" - I even tried an addition "voltron init" in my gdb init but no localhost:5555 connection available. I'll shelve this for now and maybe can submit more detailed bug report at a later date. A shame. re Python versioning ; no idea how to fix that install script - voltron does or doesn't work with a system whose default python is 2.x? eg debian. Closing.