On Tue, Nov 15, 2022 at 10:25:21PM +0100, 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?
vanguards is already on the autoremoval list due to pypy (and might even get removed before stem through python-setuptools). Making #932820 RC might be a good idea? IMHO just waiting until autoremovals sort everything out might then be good enough? > Cheers cu Adrian
