Your message dated Tue, 15 Nov 2022 22:56:27 +0100
with message-id <Y3QLC8UlQd/sg...@ramacher.at>
and subject line Re: Bug#1024178: RM: pypy-stem/1.8.0-3.1
has caused the Debian Bug report #1024178,
regarding RM: pypy-stem/1.8.0-3.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1024178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.
hefee
--- End Message ---
--- Begin Message ---
On 2022-11-15 23:43:37 +0200, Adrian Bunk wrote:
> 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?
Done
> IMHO just waiting until autoremovals sort everything out
> might then be good enough?
Or let's just remove it now. It does not look like it has an active
maintainer anyway.
Cheers
--
Sebastian Ramacher
--- End Message ---
