Update nvidia-glx-driver to 465.24.02
Changelog available here
Details
Details
- Reviewers
JoshStrobl - Group Reviewers
Triage Team - Commits
- R2210:eca067c3b5c8: Update nvidia-glx-driver to 465.24.02
Rebooted, launched Steam and played the free games "b"(Proton) and "Floating Point"
Diff Detail
Diff Detail
- Repository
- R2210 nvidia-glx-driver
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
| package.yml | ||
|---|---|---|
| 23 | Why was this changed? nvidia-glx-driver is for LTS kernel. | |
| package.yml | ||
|---|---|---|
| 23 | Because of the confusion it caused for at least one user when the description of the 32bit-package mentioned (LTS kernel), and he couldn't find the (current kernel) version of the 32bit-package (which of course is one and the same). I thought about adding a separate description for the 32bit-package, but then I saw the other driver branches handle it like this (see e.g. nvidia-390-glx) | |
| package.yml | ||
|---|---|---|
| 23 | Then a summary and description should be added for 32bit subpackage. I do not want people mistaking the main package, which is for LTS, as the normal one for their kernel, when most are running current. | |
| package.yml | ||
|---|---|---|
| 23 | Okay, will do so when I get home. I guess I should do the same thing for the nvidia-390 driver too then? (which is currently structured similar to this approach) | |
| package.yml | ||
|---|---|---|
| 23 | Yea that would be ideal. fwiw, both @DataDrake and I have always disagreed with the notion of main being LTS vs having a dedicated -lts sub-package. Not sure if that's something we want to bit the bullet and pull the trigger on yet, but we do tend to circle back to it every once in a while. | |
| package.yml | ||
|---|---|---|
| 27 | Needs to be added to summary as well. | |
| package.yml | ||
|---|---|---|
| 27 | Okay, done. This should make things even clearer :) | |