304.132/340.98

Luca Boccassi luca.boccassi at gmail.com
Tue Sep 27 11:38:21 UTC 2016


On Tue, 2016-09-27 at 08:57 +0100, Luca Boccassi wrote:
> On Sep 26, 2016 23:04, "Andreas Beckmann" <anbe at debian.org> wrote:
> >
> > according to the upstream changelog there there seems be be nothing too
> > urgent ... unless there are some CVEs coming out soon after ...
> > so I plan to have them sit around for some weeks (or the CVE) before
> > deciding which versions to upload where ...
> >
> >
> > Andreas
> 
> Ok, I have verified that the kernel modules build fine.
> 
> > PS: 370 module FTBFS against some -rt kernels (at least 4.1, 4.4):
> >
> > FATAL: modpost: GPL-incompatible module nvidia-drm.ko uses GPL-only
> > symbol 'rt_mutex_destroy'
> 
> Never tested rt kernels, do we support them? If so I can have a look at
> some point
> 
> Kind regards,
> Luca Boccassi

2 questions:

- May I go ahead and upload 370 to experimental, or do we want to wait
for 367 to reach testing (shouldn't make a difference I think, 367 is
already gone from exp)?
- Regarding the nks repo:
https://anonscm.debian.org/cgit/pkg-nvidia/nks-history.git/
I have a few doubts about the workflow there, specifically regarding
stable releases. Where/how should 304.132 and 340.98 be added? Which
parent/branch/etc/etc

Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20160927/64060f3c/attachment.sig>


More information about the pkg-nvidia-devel mailing list