splitting off nvidia-graphics-drivers-legacy-340xx
luca.boccassi at gmail.com
Mon Aug 3 00:26:40 UTC 2015
On 3 August 2015 at 01:14, Andreas Beckmann <anbe at debian.org> wrote:
> I started picking some bits back into trunk targeting sid today. The
> first bits (to branches/340) are non-intrusive bugfixes that I plan to
> include in a possible security update for jessie (we needed such for
> squeeze and wheezy ... so maybe jessie too), the second part to trunk is
> more intrusive and won't hit jessie (except via backports).
> The next bits I'll do are
> * nvidia-detect updates
> * renaming the nvidia-uvm.ko module
> These shouldn't be cherry-picked into experimental until they are
> finished and working. Especially for renaming the kernel module I could
> need some help for testing that this works properly ...
I'll gladly help out, I have 2 machines with Nvidia hardware and one
is a laptop,
so very handy for testing the nvidia uvm + cuda + bumblebee combination.
> 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).
Understood. Good stuff, thanks for doing this!
> Regarding conftest.h: there shall be exactly one version being used for
> all packages (current and legacy, sid and unstable), otherwise
> maintaining it becomes even more hell :-)
Makes sense, I agree. I will backport the fix I've done in
branches/352 to branches/340.
Should I backport to trunk as well?
> Regarding patches: I usually don't refresh patches as long as they still
> apply, that reduces the noise in the diff between branches (including
> current vs. legacy).
Ops, sorry :-)
> The packages I uploaded today (source-only uploads are sufficient for
> n-g-d) are currently stuck as BD-Uninstallable due to the ongoing
> libstdc++ transition, that should resolve itself over the next days.
> PS: @Luca: are you subscribed tp pkg-nvidia-devel@? So I can stop Cc:ing
> you :-)
I am, thanks for the concern :-)
More information about the pkg-nvidia-devel