unity-api-bugs team mailing list archive
-
unity-api-bugs team
-
Mailing list archive
-
Message #00845
[Bug 1232118] Re: Don't read manifest files directly
This bug was fixed in the package click - 0.4.9
---------------
click (0.4.9) saucy; urgency=low
* Explicitly build-depend on pkg-config, since it's needed even if the
PackageKit/GLib-related build-dependencies are removed for backporting.
* Remove some stray documentation references to Ubuntu 13.04.
* Ensure that the user's overlay database directory exists when
unregistering a preinstalled package (LP: #1232066).
* Support packages containing code for multiple architectures, and
document the "architecture" manifest field (LP: #1214380, #1214864).
* Correctly pass through return values of commands as the exit status of
the "click" wrapper.
* Extend "click info" to take a registered package name as an alternative
to a path to a Click package file (LP: #1232118).
* Force unpacked files to be owner-writeable (LP: #1232128).
-- Colin Watson <cjwatson@xxxxxxxxxx> Mon, 30 Sep 2013 15:24:49 +0100
** Changed in: click (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Upstart Application Launcher.
https://bugs.launchpad.net/bugs/1232118
Title:
Don't read manifest files directly
Status in Upstart Application Launcher:
Incomplete
Status in URL Dispatcher:
Incomplete
Status in “click” package in Ubuntu:
Fix Released
Bug description:
Upstart App Launch and URL Dispatcher are finding the manifest files and reading them to check versions and find applications. They shouldn't be finding the files at all and should be asking click for the manifests. So this bug is to track the overall change as Click doesn't yet have an interface to get the manifest for a package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart-app-launch/+bug/1232118/+subscriptions
References