-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 2019-01-09 at 00:27 +0100, Andreas Beckmann wrote:
[ cut ]
> I'll do binNMUs tomorrow (but I'll wait for pycuda to migrate to
> testing
> first).
According to
https://tracker.debian.org/pkg/pycuda
PyCUDA is stuck behind numpy, which is stuc
On 2018-11-16 06:54, Mo Zhou wrote:
> Please hold on the CUDA version for a while. Some important applications
> are still not fully ready for CUDA 10. Since recently Nvidia started to
> produce buggy software and buggy hardware, I think we should slow down
> our pace and only update CUDA when nece
On 2018-12-12 15:48, Graham Inggs wrote:
> On 2018/12/11 21:51, Andreas Beckmann wrote:
>> Which packages
>> * can be binNMUed (manually by me or another DD, not by the release team)
>> * need sourceful uploads
>> * should get sourceful uploads to change ... and ...
>> ?
>
> eztrace-contrib, hwloc
On 2018/12/12 17:21, Mo Zhou wrote:
caffe-contrib FTBFS because libopencv-dev cannot be installed,
libopencv-dev cannot be installed because there is a temporary FTBFS
against hdf5 where libvtk6-dev is uninstallable.
I'm not going deeper along the dep tree.
I should have mentioned my pre
lua-torch-cutorch is deprecated by upstream and orphaned by me:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916281
caffe-contrib FTBFS because libopencv-dev cannot be installed,
libopencv-dev cannot be installed because there is a temporary FTBFS
against hdf5 where libvtk6-dev is uninsta
On 2018/12/11 21:51, Andreas Beckmann wrote:
Which packages
* can be binNMUed (manually by me or another DD, not by the release team)
* need sourceful uploads
* should get sourceful uploads to change ... and ...
?
eztrace-contrib, hwloc-contrib and starpu-contrib all built with no
changes requ
On 2018-12-11 06:53, Graham Inggs wrote:
> On Thu, 6 Dec 2018 at 16:03, Andreas Beckmann wrote:
>> My plans are 9.2 (or 10.x if someone has time to look into it, so,
>> probably not)
>> 410.xx driver is already in NEW
>
> Ubuntu already have a 410.xx driver, so I'm keen for 9.2 to be
> uploaded t
Hi
On Thu, 6 Dec 2018 at 16:03, Andreas Beckmann wrote:
> My plans are 9.2 (or 10.x if someone has time to look into it, so,
> probably not)
> 410.xx driver is already in NEW
Ubuntu already have a 410.xx driver, so I'm keen for 9.2 to be
uploaded to unstable. I can spend some time on preparing
Hi,
On 2018-12-06 06:31, Mo Zhou wrote:
> Do you have any plan about Buster's CUDA version?
> My Recommendation is 9.2 since 9.1 is buggy.
My plans are 9.2 (or 10.x if someone has time to look into it, so,
probably not)
410.xx driver is already in NEW
I'm waiting for new a 390.xx legacy branch r
Hi Anbe,
Do you have any plan about Buster's CUDA version?
My Recommendation is 9.2 since 9.1 is buggy.
My most familiar use case of CUDA is PyTorch, which
omitted CUDA 9.1: https://pytorch.org/
control: tags -1 +moreinfo
Please hold on the CUDA version for a while. Some important applications
are still not fully ready for CUDA 10. Since recently Nvidia started to
produce buggy software and buggy hardware, I think we should slow down
our pace and only update CUDA when necessary, or when t
Package: nvidia-cuda-toolkit
Version: 9.2.148-1
Severity: wishlist
Justification: new upstream release
https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html
Some notable points from the release notes:
1. CUDA 10.0.130, requires nvidia >= 410.48
2. CUDA 10.0 adds support for the Turin
12 matches
Mail list logo
