pycuda updates (Re: testing packages against nvidia-cuda-toolkit 7.0)
anbe at debian.org
Mon Jan 18 01:03:37 UTC 2016
On 2016-01-15 22:44, Andreas Beckmann wrote:
> On 2016-01-09 20:53, Tomasz Rybak wrote:
>> I've tested PyCUDA and it works without a problem with CUDA 7.0.
>> What's the plan now? Will you upload CUDA 7.0 to unstable,
>> or (based on lumin's work) wait for 7.5?
> I have not decided, yet, but neither will happen before I have caught up
> with the drivers.
>> I'm asking because there's Python 3.5 transition (for which I'll need
>> to build and upload PyCUDA myself), so I'd like to plan accordingly.
If you are going to do a manual upload, you should drop the -dbg
packages (in favor of autogenerated -dbgsyms ones)
> That transition is ongoing. If all you need is a binNMU to pick up the
> updated dependencies, I can do that, you don't have to do a sourceful
> upload unless you have other changes or a new upstream as well.
> (I would build the binNMU locally (with the +b1 binNMU suffix), like I
> do for other non-free packages from time to time, since these cannot be
> built on the buildd network.)
I plan to backport nvidia-cuda-toolkit 6.5 for jessie-backports once
driver 352 and the newer 6.5 reach testing. Would it be useful to have
pycuda backports as well?
PS: don't forget, 7.0 drops i386 support
More information about the pkg-nvidia-devel