On 2019/08/20 09:57, Graham Inggs wrote:
The same warning does appear in the amd64 build as well. I'll try to
reproduce on plummer.debian.org.
I tried, but couldn't figure out how to enable contrib or non-free on a
porterbox. Is it even possible?
Anyway, it seems that caffe-contrib has nev
Hi Andreas
On Sat, 17 Aug 2019 at 22:37, Andreas Beckmann wrote:
> I've now uploaded it to experimental.
> Please check whether all packages B-D on n-c-t build with 10.1U1 - we
> recently had a spurious FTBFS on ppc64el while testing the 10.1 transition.
Thanks for the upload!
I sync'd 10.1.168
On 14/06/2019 17.36, Graham Inggs wrote:
> As of now, my packaging attempt builds on amd64 and ppc64el, and I'll be
> running some tests on it next week.
I've now uploaded it to experimental.
Please check whether all packages B-D on n-c-t build with 10.1U1 - we
recently had a spurious FTBFS on ppc
On Sun, 7 Jul 2019 at 12:26, Andreas Beckmann wrote:
> Wouldn't it be sufficient if we relax the driver version in the
> dependencies to the mayor driver version (no digits) instead of tracking
> two versions?
I don't know. From the bits I've read, it sounds like Nvidia want to
release the CDUA
On 07/07/2019 11.38, Graham Inggs wrote:
>> From looking at the diff some time ago I remember you added a new
>> variable for the driver version. Why?
>
> The minimum driver version and the version included in the download
> filename are now different [3].
Wouldn't it be sufficient if we relax th
Hi Andreas
On Sun, 7 Jul 2019 at 11:16, Andreas Beckmann wrote:
> I think I'll upload 10.1 to sid first, do the transition there (do you
> remember any problems from Ubuntu?)
No problems; most were no-change rebuilds (aka binNMUs), except
caffe-contrib [1] and starpu-contrib [2] where I switched
On 14/06/2019 17.36, Graham Inggs wrote:
> Hi all
>
> On 2019/06/12 14:23, Andreas Beckmann wrote:
>> Nice. I'll look into this next month (after buster was released).
I think I'll upload 10.1 to sid first, do the transition there (do you
remember any problems from Ubuntu?) and look at 10.1u1 aft
Hi all
On 2019/06/12 14:23, Andreas Beckmann wrote:
Nice. I'll look into this next month (after buster was released).
I was keen to try the new version to see if it solved a problem with
p2pBandwidthLatencyTest locking up on a machine with two TITAN X GPUs,
so I went ahead and pushed a 10.1u
On 11/06/2019 15.36, Graham Inggs wrote:
> CUDA 10.1 Update 1 (10.1.168) was released at the end of May, 2019. The
> minimum NVIDIA driver version remains at 418.39 and support is added for
> Clang 8.
Nice. I'll look into this next month (after buster was released).
Andreas
Source: nvidia-cuda-toolkit
Version: 9.2.148-6
Severity: wishlist
Hi Maintainers
CUDA 10.1 Update 1 (10.1.168) was released at the end of May, 2019. The
minimum NVIDIA driver version remains at 418.39 and support is added for
Clang 8.
As per the release notes [1]:
"CUDA 10.1 Update 1 is a m
10 matches
Mail list logo
