changes after n-g-d 194.36.31-4
Andreas Beckmann
debian at abeckmann.de
Mon Sep 27 08:36:43 UTC 2010
Hi,
the 71xx packages are ready for a new upload to unstable. They are not
usable in testing/unstable, but they are now (nearly) installable in
lenny (see below) and may work as a base for backports if anyone is
interested. Since they depend on xserver-xorg-core from lenny, they
can't migrate to testing accidently.
I did a lot of install/upgrade tests of the packages uploaded recently
and found a few missing Breaks in libgl1-nvidia-alternatives: partial
upgrades from some bad old nvidia-glx*-dev package may break
libgl1-nvidia-alternatives. This is fixed in -5. I also adjusted some
more dependencies, so the package is (nearly) installable in lenny.
I included the changes from 256.53-2 in my tests and recommend that we
merge them into 194.36.31-4:
* remove 2 unused packages libcuda1-dev and nvidia-libopencl1-dev
- they exist in testing (but not lenny) and their only user is nvidia-
cuda-toolkit (in NEW only)
- they will be removed in 256.xx anyway
- the upgrade(removal/disappearing) path is clean and works without
transitional packages (old libfoo-dev depends on libfoo and new
libfoo will Conflicts/Replaces libfoo-dev afterwards, there is no
Depends/Recommends: nvidia-cuda-toolkit being added since this is
currently not available)
* module build updates
- looks fine, I had no problems building modules with module-
assistant and these changes
None of the (proposed) changes in -5 need to be applied to 173xx and
96xx legacy packages right now.
Anyway, we need to fix libgl1-nvidia-alternatives and therefore need an
approval from Julien, again.
Looks like you will have to file package removal requests for
libgl1-nvidia*-dev (and libcuda1-dev, nvidia-libopencl1-dev if we remove
them in -5) since they are no longer being built from source and are now
outdated (probably blocking testing migration).
Backports to lenny:
I successfully installed the nvidia-graphics-drivers (and
nvidia-graphics-drivers-legacy-71xx) (excluding the *-ia32 packages due
to the /emul/ia32-linux to /usr/lib32 transition) in a
lenny + lenny-backports + dpkg(from testing) chroot. dpkg 1.15.x is
required for dpkg-maintscript-helper and dpkg-divert --listpackage.
The *-ia32 packages all have a proper Pre-Depends on a glibc not
satisfyable in lenny and the maintainer scripts of the other packages
now (i.e. -5) depend on proper versioned dpkg (if needed) to avoid failures.
So if anyone wants to do lenny-backports, he will need to backport dpkg
first and then just disable the -ia32 packages. Everything else needed
seems to be available in lenny-backports, but I didn't try a package
build in a lenny-backports environment.
Something I couldn't test so far is doing a dist-upgrade from lenny to
testing/sid.
For the new upstream versions I would recommend the Debian NVIDIA
Maintainers Team does "official" backports to squeeze. Another reason
why I'd like to get rid of the two superfluous -dev packges right now.
Having current drivers available for stable is something the users most
probably want to have.
Andreas
More information about the pkg-nvidia-devel
mailing list