[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#750575: Stuff still needing doing for python3.3 removal



Not sure if the following is going to help but since I had some spare
minutes… TL;DR: look at upstart and morse-simulator.

Scott Kitterman <debian@kitterman.com> (2014-06-13):
> Checking reverse dependencies...
> # Broken Depends:
> bpython: bpython3

arch:all but a simple rebuild seems to make it switch from 3.3 to 3.4.

> cherrypy3: python3-cherrypy3

arch:all but a simple rebuild seems to make it switch from 3.3 to 3.

> doit: python3-doit

arch:all but a simple rebuild seems to make it switch from 3.3 to 3.

> libpeas: libpeas-1.0-0 [hurd-i386]

hurd, shrug.

> morse-simulator: python3-morse-simulator [kfreebsd-i386]

build-attempted, 3 times.

> pystache: python3-pystache

arch:all but a simple rebuild seems to make it switch from 3.3 to 3.4.

> python-json-patch: python3-jsonpatch

arch:all but a simple rebuild seems to make it switch from 3.3 to 3.4.

> retext: retext

arch:all but a simple rebuild seems to make it switch away from 3.3.

> upstart: upstart-monitor

arch:all and a simple rebuild does NOT make it switch away from 3.3.
I suspect this is due to the following line in debian/control:
| X-Python3-Version: 3.3

> uwsgi: uwsgi-plugin-python3 [sparc]

sparc, shrug.

> zope.testrunner: python3-zope.testrunner

arch:all but a simple rebuild seems to make it switch from 3.3 to 3.4.


> # Broken Build-Depends:
> morse-simulator: python3.3-dev

From the changelog, not sure what happened to your changes to switch
away from 3.x specifics, maybe some mismerge at some point? Better
talk to the maintainer directly I guess.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


Reply to: