getting nvidia-cuda-toolkit into testing

[Russ Allbery]

Andreas Beckmann <debian at abeckmann.de> writes:

> do we need to do something special to get nvidia-cuda-toolkit 4.x into
> testing?
> http://release.debian.org/migration/testing.pl?package=nvidia-cuda-toolkit
> Do we need to file removal bugs for the obsolete library packages?
> Or is this automatic, but did not yet pick up the amd64 upload because
> it says:
>     nvidia-cuda-toolkit is not yet built on amd64: 3.2.16-2 vs 4.0.17-2
>     (missing 10 binaries)
> Which is wrong ...

ftpmaster needs to remove the old binary packages, which is semi-automated
but requires someone to kick it off by hand.  That happens periodically
and it should just be a matter of waiting for a few days.  Then, it looks
like the release team may have to hint nvidia-cuda-toolkit and
khronos-opencl-headers in together, since it looks like they both break
the other package in testing?

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>