Jockey will fail against local disk archive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
jockey (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
Ubuntu 11.10
Jockey 0.9.4-0ubuntu10
Some logic looks problematic and is causing jockey to fail to find drivers on our on-disk repositories. Local on-disk archives are used a lot in OEM on customer's first boot. We are currently carrying patches to Jockey for a number of OEM projects to get around this.
I have found 3 issues in the code related to this:
1. The code in OSLib::
2. There is also a similar problem in the detection.py code - DriverDB:
m = re.match(
if m:
u = m.group(1)
But I'm not sure if that's sufficiently tight? Perhaps ".*(file:
3. The on-disk binary drivers will be unsigned, so will fail. I would think an appropriate solution would be to allow the signature checking to be turned off with a command line option.
description: | updated |
description: | updated |
Changed in oem-priority: | |
importance: | Undecided → High |
status: | New → Confirmed |
status: | Confirmed → New |
Changed in oem-priority: | |
assignee: | nobody → Ursula Junque (ursinha) |
tags: | added: rls-mgr-p-tracking |
tags: | removed: patch |
Changed in jockey (Ubuntu): | |
status: | Incomplete → In Progress |
assignee: | nobody → Martin Pitt (pitti) |
importance: | Undecided → Medium |
Changed in oem-priority: | |
status: | Incomplete → In Progress |
Changed in oem-priority: | |
assignee: | Ursula Junque (ursinha) → nobody |
tags: |
added: rls-p-tracking removed: rls-mgr-p-tracking |
Changed in jockey (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in oem-priority: | |
status: | In Progress → Fix Released |
I initially thought this was a newly introduced issue in the -proposed version, but I was wrong - edited but to reflect this.