EnvyNG installs Ubuntu's lrm but it should install its own packages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
envyng-core (Ubuntu) |
Fix Released
|
Undecided
|
Alberto Milone | ||
Hardy |
Fix Released
|
Undecided
|
Alberto Milone | ||
linux-restricted-modules-envy-2.6.24 (Ubuntu) |
Fix Released
|
Undecided
|
Alberto Milone | ||
Hardy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: envyng-core
EnvyNG used to install the restricted modules from my PPA however, because of some concerns about security, EnvyNG no longer does so and relies on Ubuntu's default linux-restricte
https:/
This makes pointless the use of EnvyNG since the packages which it's supposed to install contain improvements (e.g. support for CUDA and dkms). As Steve Langasek pointed out, it is not possible to have linux-restricte
A possible solution would be to build EnvyNG's restricted modules with different names so that for example we have packages like nvidia-
Dist-upgrades to Intrepid Ibex won't be broken if we make sure that Intrepid's restricted packages (in main) replace (by using something like “Replaces: nvidia-
TEST CASE: a user installs EnvyNG and expects it to install the packages with all the features which EnvyNG used to deliver.
Of course I'm open to other solutions.
Related branches
Changed in envyng-core: | |
assignee: | nobody → albertomilone |
status: | New → Confirmed |
In Intrepid final, those -envy packages should just be transitional packages to nvidia-glx-new, etc., and those should have proper Conflicts/Replaces. That way, a dist-upgrade to intrepid will go back to the l-r-m ones (which are current at that time), but we can update-envy packages again in intrepid-updates.
Please attach a debdiff for approval, I'll help you with sponsoring.