Updating nvidia-driver to 346.xx, and split separate nvidia-340 source package?

[Vincent Cheng]

Hi Andreas,

On Thu, May 14, 2015 at 1:35 AM, Vincent Cheng <vcheng at debian.org> wrote:
> Hi Andreas,
>
> On Tue, May 12, 2015 at 1:19 PM, Andreas Beckmann <anbe at debian.org> wrote:
>> On 2015-05-12 10:42, Vincent Cheng wrote:
>>> Hi Andreas (and everyone else following on the list),
>>>
>>> Is there a documented process on how to update and split a separate
>>> legacy driver package? Aside from actually creating and uploading a
>>> new "nvidia-graphics-drivers-legacy-340xx" source package, what other
>>> packages need to be updated in lockstep?
>>
>> This time nvidia-graphics-drivers-legacy-340xx will be a bit more
>> involved since we need to rename more kernel modules ... as well as
>> doing something with cuda as well.
>
> Ack, I suspected there was more work involved...
>
>> Anyway I pushed 346.59 to experimental to add support for a bunch of new
>> hardware.
>> I'd prefer to have a working legacy-340xx in unstable before moving
>> nidia-graphics-drivers to a new upstream release there (>> 340),
>> unfortunately I didn't find the time to look into the new legacy one yet
>> after the jessie release.
>> It will be the first thing for me to handle once I'm back from holidays
>> in the first week of June.
>
> Good to hear, thanks! I guess for now I'll work on some of the easier
> tasks outside of the transition (nvidia-graphics-modules needs to be
> updated now that linux 4.0 is in sid, and a new upstream 346.xx
> release was made that should be packaged for experimental; I'll tackle
> those first).
>
> Once the transition is all complete, I think we'd want to backport
> 346.xx to jessie as well for the added hardware support, right?

Hmm...it also looks like the nvidia-graphics-drivers/346.59-1 upload
you made a few days ago FTBFS (patches don't apply cleanly)? I'll take
a look soon-ish if you aren't already doing so.

Regards,
Vincent