[Bug 913927] Re: Jockey will fail against local disk archive

[Ubuntu Foundation's Bug Bot]

The attachment "jockey.diff" of this bug report has been identified as
being a patch in the form of a debdiff.  The ubuntu-sponsors team has
been subscribed to the bug report so that they can review and hopefully
sponsor the debdiff.  In the event that this is in fact not a patch you
can resolve this situation by removing the tag 'patch' from the bug
report and editing the attachment so that it is not flagged as a patch.
Additionally, if you are member of the ubuntu-sponsors team please also
unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by
Brian Murray.  Please contact him regarding any issues with the action
taken in this bug report.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/913927

Title:
  Jockey will fail against local disk archive

Status in OEM Priority Project:
  Incomplete
Status in “jockey” package in Ubuntu:
  Incomplete

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::has_repositories assumes URIs - "://" from apt-
  cache policy.  If the archive is file based it will be
  "file:/foo/bar/..." and so will not satisfy the test.

  2.  There is also a similar problem in the detection.py code -
  DriverDB::_cache_id(self), which also assumes a "://".  When I altered
  it to this (along with fixing the above) jockey worked as I would
  hope:

      m = re.match(".*::/{1,2}(.*)")
      if m:
           u = m.group(1)

  But I'm not sure if that's sufficiently tight?  Perhaps
  ".*(file:/|://)(.*)", and then group(2)?

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/913927/+subscriptions