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

[Adam D. Barratt]

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

There's also an auto-hint which pulls in hwloc-contrib, but also fails:

Trying easy from autohinter: nvidia-cuda-toolkit/5.0.35-5 
hwloc-contrib/1.7.1-1
leading: nvidia-cuda-toolkit,hwloc-contrib
start: 30+0: i-3:a-1:a-1:a-2:i-1:k-5:k-5:m-1:m-1:p-1:s-2:s-4:s-3
orig: 30+0: i-3:a-1:a-1:a-2:i-1:k-5:k-5:m-1:m-1:p-1:s-2:s-4:s-3
easy: 47+0: i-12:a-9:a-1:a-2:i-1:k-5:k-5:m-1:m-1:p-1:s-2:s-4:s-3
     * i386: libhwloc-contrib-plugins, 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
     * amd64: 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.

Regards,

Adam