why is nvidia-cuda-toolkit not migrating to testing?

[Samuel Thibault]

Adam D. Barratt, le Fri 05 Jul 2013 10:20:57 +0100, a écrit :
> On 2013-07-05 9:01, Adam D. Barratt wrote:
> >On 2013-07-05 8:15, Andreas Beckmann wrote:
> >>could someone give a little kick to nvidia-cuda-toolkit [non-free] so
> >>that it moves towards testing? Or is there something blocking this but
> >>not listed in the excuses?
> >
> >The britney log says:
> >
> >trying: nvidia-cuda-toolkit
> >skipped: nvidia-cuda-toolkit (4 <- 309)
> >    got: 11+0: i-11
> >    * i386: libsocl-contrib-1.0, libstarpu-contrib-1.0,
> >libstarpu-contrib-dev, libstarpu-contribfft-1.0,
> >libstarpu-contribmpi-1.0, python-pycuda, starpu-contrib-examples,
> >starpu-contrib-tools
> [...]
> >pycuda was recently uploaded and built against libcurand5.0, but is
> >only 3/10 days old. A test with it aged still fails on starpu-contrib,
> >because it depends on the old cuda libraries; I've scheduled binNMUs.
> 
> Which of course won't work, because the buildds won't pull in n-c-t from
> non-free (-EMORECOFFEE); adding the starpu-contrib maintainers to CC, as
> it'll need separate uploads.

I have uploaded starpu-contrib with fixes for automake and built against
sid's current nvidia packages.

Samuel