[pkg-nvidia-devel] Anything waiting for upload?

[Andreas Beckmann]

Russ Allbery wrote:
> Andreas, have you started looking at the legacy packages yet?  I have a
> 173xx card that I can use for testing.  It sounded like you had a plan for
> how you wanted to deal with them.

Once 195.36.24-3 is out, I plan to update 173xx and finalize
nvidia-graphics-modules.

I think nvidia-graphics-drivers is ready for upload, but it should be
tested a bit more to check all upgrade paths. If you see an error during
upgrades saying
  "ln: /usr/lib/libGL.so: link exists"  (or similar wording)
it's from the init script which is called from
  "<old-prerm> upgrade <newversion>"
i.e. before we have a chance to remove it :-)

The trigger may be a bit too verbose, we can silence it later if neccessary.

Please check the NEWS file.

Did you think about marking the non-free packages as automatically
buildable?

After the recent reorganisation, we might even reconsider the decision
about not providing libgl1, IMO we could try to actually provide it
(didn't test it, yet).

libvdpau, nvclock and nvidia-xconfig should be ready, too, except for
some TODO mentioned at top of the changelog.

Should we add a "Provides: nvidia-glx-whatever" to
nvidia-glx{,-legacy-ABCxx} (the name of that virtual package still needs
to be decided), so that addon packages could just
"Suggests: nvidia-glx-whatever" instead of the full list of
alternatives? Also fglrx-glx could just "Conflicts: nvidia-glx-whatever"

Should we change nvidia-kernel-common from
arch: all to arch: amd64 i386? Even if it is buildable everywhere, it is
only useful on platforms that actually have NVIDIA kernel modules.

Same question goes for nvidia-xconfig (is it even still useful?) and
nvclock (there is bug #551096) that are arch: any. But these packages
you actually might use on other platforms that don't have NVIDIA driver
support.


Andreas