touch-packages team mailing list archive

Thread
Date

[Bug 1319030] Re: Can't combine custom registry with system server scope proxy

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Michal Hruby <michal.hruby@xxxxxxxxxxxxx>
Date: Fri, 11 Jul 2014 12:07:01 -0000
Reply-to: Bug 1319030 <1319030@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: unity-scopes-api (Ubuntu)
       Status: New => Fix Released

** Changed in: unity-scopes-api
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1319030

Title:
  Can't combine custom registry with system server scope proxy

Status in API for Unity scopes integration:
  Fix Released
Status in “unity-scopes-api” package in Ubuntu:
  Fix Released

Bug description:
  One of the use cases in unity-scope-tool is spawning a custom non-
  installed scope (using `../scoperegistry tmp_runtime.ini
  path_to_scope.ini`), but at the same time being able to talk to the
  system-wide smart-scopes-proxy.

  It seems this is no longer possible after recent config changes - all
  endpoints have to be in the same directory - and the tmp_runtime.ini
  will use different endpoint dir than the system-wide smart-scopes-
  proxy is.

  What's the desired solution to this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-scopes-api/+bug/1319030/+subscriptions