[Debian-med-packaging] [Python-modules-team] Any reason why python-numpy version 1.9.2 is in experimental?
Andreas Tille
andreas at an3as.eu
Wed Aug 5 06:09:10 UTC 2015
Hi Kevin,
On Wed, Aug 05, 2015 at 10:09:08AM +1000, Kevin Murray wrote:
> >
> > 1. Do nothing and wait until #794511 will be fixed. This will put an
> > RC bug on python-skbio 0.4.0 since it will not build from source.
> > 2. Upload to experimental and remove from unstable.
> > 3. Use an epoch and upload 1:0.2.3-1 to unstable
>
> I reckon that either option 1 or 3 or some combination of the two would be the
> best option. Is it a bad idea to have skbio 0.2.3 in unstable now (for QIIME's
> sake at least), and deal with 0.4.0 when numpy becomes installable? I am
> running sid here on my laptop, and there's a whole heap of uninstallable
> updates due to the libc++6/gcc5 issues, so I don't think we'll be alone
> whatever happens.
I think we simply stick to 1. You are right that the libc++6 transition
is breaking a lot of stuff and once it is finished python-skbio 0.4.0
will be fine automatically anyway.
BTW, in these times I'm happy to run testing on my machines. ;-)
Regarding QIIME you have probably seen my ITP of sortmerna. I also
intent to take over sumatra from BioLinux PPA. If you intend to
co-maintain these packages as well I'll move to Git. Just let me know.
Kind regards
Andreas.
--
http://fam-tille.de
More information about the Debian-med-packaging
mailing list