splitting off nvidia-graphics-drivers-legacy-340xx
luca.boccassi at gmail.com
Wed Aug 12 09:03:37 UTC 2015
On 12 August 2015 at 09:44, Andreas Beckmann <anbe at debian.org> wrote:
> On 2015-08-07 09:17, Vincent Cheng wrote:
>>> Once all this is working and in sid, it will be easy to finally split
>>> off the new 340xx legacy package (and upload newer releases to sid).
> This was just uploaded and very quickly passed through NEW.
> Unfortunately I won't have time to test it before holidays, but you are
> welcome to do so :-) It should be installable along the driver from
> experimental, not the driver from unstable (which is the same version
> and therefore needs some Conflicts).
> I hope we can stick with nvidia-graphics-drivers 340.xx in sid for one
> more month, so I can continue upgrading things in September.
> The 355.xx releases (a beta is out) will change the layout of the kernel
> module source (and may even bring new modules), but new 352.xx releases
> hopefully won't do this change, yet. I'll look into this once
> experimental is "free" after unstable got 352.xx.
> I completely missed that 340.xx is sufficient for nvidia-cuda-toolkit
> 6.5 (only 7.0 needs 346.xx), so I didn't think about starting that
> transition so far. Now we will have to wait for the libstdc++v5
> transition to finish.
> And once all this is over (most likely with 355+ in sid), I'm looking
> forward to maybe unifying the nvidia-settings packaging with Ubuntu.
Thanks for doing the work! In the next few days I'll give it a try on
my machines and see how it goes.
Regarding 355, I started doing the legwork. I got the modules building
and installing, all is left is updating the libEGL, as the name of the
binary Nvidia ships changed. Once I have it in a working state, I'll
branch 352 and create branches/355 and upload it there for review.
Regarding 352, 352.30 is still stuck with Need-Build on buildd ,
anything we can do about it?
More information about the pkg-nvidia-devel