envy needs to pull drivers from multiverse, not PPA
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
envyng-core (Ubuntu) |
Fix Released
|
Medium
|
Alberto Milone |
Bug Description
Binary package hint: envyng-core
Envy's drivers need to come from multiverse. Regular QA and sponsoring should not be time-consuming to obtain when doing bleeding-edge driver updates. Repeated from bug 210112:
Security concerns: while people using Envy are already directly installing software from a non-official repository, if they switch to EnvyNG, they are no less safe. However, since EnvyNG is installable from the repo directly now, it is likely there will be more people installing it, which means more people will be potentially vulnerable to a breach of the PPA driver updates. It would be better if updates were being reviewed by motu or core-dev for issues. Doing full testing is out of scope, since the whole purpose of envy is to provide bleeding-edge drivers.
License concerns: are the drivers in the PPA redistributable? I assume so, since they're in a PPA. If so, why can't they be put into multiverse? They don't change so often that it would be a burden to do SRUs for them, especially if a standing SRU exception was made for Envy drivers.
Related branches
Changed in envyng-core: | |
importance: | Undecided → Medium |
milestone: | none → ubuntu-8.04 |
status: | New → Confirmed |
description: | updated |
Changed in envyng-core: | |
assignee: | nobody → albertomilone |
status: | Confirmed → In Progress |
EnvyNG no longer enables my PPA but tries to enable both universe and multiverse. It's all in revision 45 of the bzr branch of envyng-core: /code.launchpad .net/~albertomi lone/envy/ envyng- core
https:/
As regards the drivers I have modified only the debian/ control. stub.in and the changelog. If you want to check them you can get the source code from my PPA: /launchpad. net/~albertomil one/+archive
https:/