Re: python3.3 status
On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote:
> Here's a further update on packages pertaining to the 3.3 transition:
>
> libguestfs - No longer FTBFS on amd64, but does on i386, #710545, now
> builds for all python3 versions
> nuitka FTBFS unrepoducible
pyepr builds successfully, but puts dbg extensions into wrong package:
#708011 - bug marked as pending
pyside Fixed, needs python3.3 as default to migrate to testing, nothing
further to do for transition
python-scipy FTBFS with new Cython/Numpy: #707315 Needs new, new cython
which is ready in svn, needs new upstream release, needs python3-imaging
> pytango - FTBFS on s390 -> #711761
morse-simulator - NMUed for #712014 - will need binNMU after python3.3 is
default
pyopencl package fixing FTBFS #711926 is in NEW now.
> boost1.53 - builds, but doesn't generate python related depends right (not
> related to the transition)
> 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 - Builds fine, no action needed for transition, ideally would
> build- dep on python3-all
> subunit - No action needed for transition, but multiple bugs need dealing
> with, #708077, #709540, and #712203
> yafaray - FTBFS fixed. Only supports default python3, so it will need
> binNMU after python3.3 is default.
shiboken - built on mipsel finally, all done
> 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 dependency. It'd be nice if someone could have a look.
> python-astropy Builds fine, but doesn't actually put the python3 build in
> a binary, no impact on the transition
I've marked the things that I think block python3.3 as default a blocking
the transition bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708536
Is there anything there that shouldn't be a blocker? I think scipy is the
biggest issue and that apparently needs cython updated first.
Scott K
Reply to: