Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #11614

Bug#934333: Investigating the reverse dependencies of python-monotonic.

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

(note for people reading on bug 934333, the start of this thread can be found at https://lists.debian.org/debian-python/2019/08/msg00070.html )

On 13/08/2019 11:54, Andrey Rahmatullin wrote:
> This is worrying, a package with revdeps shouldn't have been dropped.

AIUI a "go cleanly" approach was agreed at the Python BoF, but by that time an aggressive removal process was already well underway for django and openstack related packages.

> By the way, you checked only deps, not build-deps, as at least
> python-coloredlogs and python-datalad has reverse build-deps.

I took a look at the build-rdeps, also this time I used unstable whereas my previous analysis had been looking at buster (yeah, this made little sense, I was probablly meaning to use bullseye but mixed the words up in my head, not that I think it made any difference). Again i'm not investigating openstack related stuff. This seems to add a few more packages to our set

python-jira (via python-tenacity)
cyvcf2 (via python-coloredlogs, sid version has dropped the python2 stuff, but it's blocked from having old versions cleaned up and migrating to testing by build failures on mips*)
heudiconv (via python-datalad, sid only, never been in testing or a stable release, WTF was someone doing uploading a new python2 only package in 2019?!)
python-googlecloudapis (via python-oauth2client, sid only)
python-google-auth(via python-oauth2client, sid only)
rekall(via python-oauth2client)
python-oslo.cache (via python-etcd3gw, openstack related)
elastalert (via python-jira, also depends on python-croniter)

> I've also noted https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934333
ccing this mail there.
>
> As for duplicity, the latest upstream version (not packaged) support
> Python 3.
There is a bug report for it, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929949

In a response to bug 934333 Ondrej Novy wrote:
> just my two cents: correct solution is to add Python 3.x support to
> python-m2crypto and migrate oz to Python 3.
I agree that is the correct long term soloution, however as mentioned in this mail and in https://lists.debian.org/debian-python/2019/08/msg00070.html it's not just oz that is involved here.
> Reintroduction Python2 support to python-monotonic is not good idea, we are
> going to drop Python 2 completly from Debian.
I understand that dropping python 2 is the goal, but my understanding of https://lists.debian.org/debian-python/2019/07/msg00069.html and https://lists.debian.org/debian-python/2019/07/msg00080.html is the plan was to do it cleanly, starting with leaf stuff and working down the dependency stack.

IMO python-monotonic should be reinstated until it's reverse dependencies are sorted out.

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Investigating the reverse dependencies of python-monotonic. peter green <plugwash@p10link.net> - 2019-08-13 12:50 +0200
  Re: Investigating the reverse dependencies of python-monotonic. Andrey Rahmatullin <wrar@debian.org> - 2019-08-13 13:00 +0200
    Bug#934333: Investigating the reverse dependencies of python-monotonic. peter green <plugwash@p10link.net> - 2019-08-13 15:40 +0200
  Re: Investigating the reverse dependencies of python-monotonic. Simon Josefsson <simon@josefsson.org> - 2019-08-13 22:40 +0200
    Re: Investigating the reverse dependencies of python-monotonic. Simon Josefsson <simon@josefsson.org> - 2019-08-15 15:20 +0200

csiph-web