Re: python3.3 status
On Wednesday, June 12, 2013 03:13:38 PM Scott Kitterman wrote:
> On Wednesday, June 12, 2013 12:48:45 AM Scott Kitterman wrote:
> > On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote:
> More updates and added all the "unknown" packages from the transition
> tracker. Items marked as fixed in the last update have been removed.
>
> > > On Thursday, May 23, 2013 06:19:06 PM Scott Kitterman wrote:
> > > > I've been working on this a bit ...
> > > >
> > > > On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote:
> > > > > python3-defaults maintainer(s?) decided to make python3.3 a
> > > > > supported
> > > > > version without prior notice. Yay. Now we have dozens of packages
> > > > > failing to build:
boost1.49 FTBFS TODO (could not find an open bug) - I plan to ignore this
this and wait until the boost1.53 transition starts and we can not care.
> flufl.bounce FTBFS #707086, needs new zope.interface
> hivex FTBFS fixed, but still doesn't generate dependencies right #709516
> libguestfs - No longer FTBFS, only builds for default python3, will need
> binNMU after python3.3 is default
> nuitka FTBFS unrepoducible
> pyepr builds successfully, but puts dbg extensions into wrong package:
> #708011
pyopencl FTBFS, #711926, maintainer is active on this
pyside Fixed by Odyx
> python-astropy Builds fine, but doesn't actually put the python3 build in
> a binary, no impact on the transition
> python-cffi FTBFS TODO
> python-csb FTBFS TODO
python-distutils-extra Builds fine now, no issues
> python-scipy FTBFS with new Cython/Numpy: #707315 Needs new, new cython
> which is ready in svn
> python-stem FTBFS TODO
> python-wadllib FTBFS #686332
pytango - Shouldn't have been removed, FTBFS on s390 - #711761
> yapsy FTBFS TODO
> zope.interface - Needs update to 4.0.2 or later, needs updated
> zope.exceptions zope.exceptions needs updated to 4.0.1
> zope.component update to 3.11.0 due to code shifted between interface and
> component.
> > morse-simulator - Builds, but depends are FUBAR: #712014
> >
> > Many of the FTBFS packages above could probably stand to be rebuilt again
> > to see if they build now (most of the ones I've tried do).
> >
> > Getting zope.interface/exceptions updated would be helpful as well, but
> > seems to need sponsoring. Arnaud Fontaine is looking into this.
> >
> > All of the red in
> > http://release.debian.org/transitions/html/python3.3.html
> > is due to open bugs (except pyside, I didn't get to look at that yet).
> > The
> > binNMUs that could be done after python-numpy was uploaded are done except
> > those blocked by bugs. It would still be worth doing some investigation
> > of the unknown packages to see if they are generating dependencies
> > correctly.
>
> Here's the other unknown packages:
>
> boost1.53 - builds, but doesn't generate python related depends right
> file - No effect on the transition #709269
> liblouis - Shouldn't be part of the transition, build-dep is wrong #712076
libsigrokdecode - #709406 marked pending since May 28, can ignore
postgresql-9.1 - Only depends on libpython3.2. Will need NMU after 3.3 is
default. I think this should have an interpreter dependency as well, but
didn't file a bug as I'm not sure. I would appreciate it if someone would have
a look.
> pycxx - Will need sourceful update after python3.3 is default
pymongo - If it was packaged properly, it would need a binNMU, but it's not,
so it's not an issue for the transition, #712112.
> sqlalchemy
> subunit
> yafaray
> znc
> magics++ - No python3 content in the binaries, no effect on transition
> pygrib - Doesn't actually build python3 packages yet, no effect on
> transition.
uwsgi - uwsgi-plugin-python3 only depends on libpython3.2 (and also 3.3 when
rebuilt). Like postgresql-9.1, I think this should probably have a python3
dpeendency. It'd be nice if someone could have a look.
>
> The list is getting smaller ...
>
> Scott K
Reply to: