On Sun, 2016-09-18 at 21:18 +0200, Andreas Beckmann wrote:
> On 2016-09-14 13:01, Luca Boccassi wrote:
> > This is already fixed in SVN, pending upload.
>
> Uploaded to unstable (361xx). Does this need updating for 364 (which
> adds another kernel module)?
>
>
> Andreas
No more changes needed f
On Sep 18, 2016 20:21, "Andreas Beckmann" wrote:
>
> On 2016-09-14 13:01, Luca Boccassi wrote:
> > This is already fixed in SVN, pending upload.
>
> Uploaded to unstable (361xx). Does this need updating for 364 (which
> adds another kernel module)?
>
>
> Andreas
Didn't think so but will double ch
On 2016-09-14 13:01, Luca Boccassi wrote:
> This is already fixed in SVN, pending upload.
Uploaded to unstable (361xx). Does this need updating for 364 (which
adds another kernel module)?
Andreas
control: forcemerge 834446 837753
On Wed, 2016-09-14 at 10:42 +0200, Tomas Janousek wrote:
> Package: nvidia-kernel-dkms
> Version: 367.44-1
> Severity: normal
> Tags: patch
>
> Similar to #815986, since 361.45.18-2 hit testing (and thus my computer), it
> doesn't build due to nv-modeset-interfac
Package: nvidia-kernel-dkms
Version: 367.44-1
Severity: normal
Tags: patch
Similar to #815986, since 361.45.18-2 hit testing (and thus my computer), it
doesn't build due to nv-modeset-interface using an incorrect command line
during linking. I'm attaching a patch that fixes this.
-- System Infor
5 matches
Mail list logo