Hey, > Migration of python-step is currently blocked as removal of pypy-stem > would render vanguards uninstallable. So what's the plan regarding > vanguards?
The pypy-stem was already a broken package and not functional it broke the autopkgtests see #1022111. Vanguards should be ported to python3 anyways and than we can create a pypy3-stem package. Just a remark - me is not the python- stem maintainer and the removal was done via a MNU by Bastian Germann (b...@debian.org)... regards, hefee -- On Dienstag, 15. November 2022 22:25:21 CET Sebastian Ramacher wrote: > Control: tags -1 moreinfo > > Hi Hefee > > On 2022-11-15 21:53:23 +0100, Hefee wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian....@packages.debian.org > > Usertags: rm > > X-Debbugs-Cc: he...@debian.org, > > pkg-privacy-maintain...@alioth-lists.debian.net > > > > The pypy-stem package is broken, as pypy is a Python 2 interpreter and > > stem code is written for Pythno 3 only. Additionally Pypy is marked for > > removal #1011926. The new python-stem version 1.8.1-1.1 is not building > > pypy-stem anymore. So the removal of pypy-stem in testing would enable > > the > > migration of python-stem and would untangle it from pypy removal. > > > > And would finally help the new onionshare version to migrate to > > testing, as it depends on the new version of python3-stem. > > Migration of python-step is currently blocked as removal of pypy-stem > would render vanguards uninstallable. So what's the plan regarding > vanguards? > > Cheers
signature.asc
Description: This is a digitally signed message part.
