On 23/01/11 04:53, Cameron Hutchison wrote:
"tv.deb...@googlemail.com"<tv.deb...@googlemail.com> writes:
The problem with extraversion and 2.6.37 is known, it's been reported
here if I remember, look for a message starting with "kernel-package:
2.6.37" in the archives. But since it seems to affect only proprietary
software I guess they'll have to adapt.
Since I was the one to report that, I should correct some things I got
wrong. The problem also exists in 2.6.36 - that's when it was
introduced, and I had to revert two commits to fix it:
7b8ea53d7f1865cd8f05dfb8f706a4ff5a72abcf (makefile: not need to
regenerate kernel.release file when make kernelrelease)
01ab17887f4cdcb8bb5a5d1bc3b160d186e6e99b (Makefile: "make kernelrelease"
should show the correct full kernel version)
I don't know if this is related to the OP's issues - I don't use nvidia
drivers.
I'm afraid it's a bit beyond my skills at the moment - I guess it's
about getting source tree by svn and reverting the changes applied by
getting previous version of a file?
Thanks anyway - I hope it will start working for me at some point :)
--
Kind regards,
Michal R. Hoffmann
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d3dee86.2090...@o2.pl
