[MIR] geoclue-2.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
geoclue-2.0 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
geocode-glib (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Availability:
geoclue-2.0 is built and available on all current architectures in vivid
Rational:
geoclue-2.0 is the current supported release of geoclue. Due to the difficulty of transitioning all packages to the new release, geoclue 1 is in a separate source package (already in main). Version 2.0 is now required by a number of gnome components in main, so it would be nice if we didn't have to carry revert patches. Currently empathy, gnome-settings-
Security:
No CVEs, active upstream, the unsupport versedion is in ubuntu already
Quality assurance:
No bugs found in debian or ubuntu for this source package (23 minor bugs for the version already in main). Active debian maintainer.
Dependencies:
All dependancies are in main
Maintenance:
Package is well maintained in debian and the ubuntu-gnome team will maintain it in ubuntu
Background information:
GeoClue is a D-Bus geoinformation service. The goal of the Geoclue project is to make creating location-aware applications as simple as possible.
description: | updated |
Changed in geocode-glib (Ubuntu): | |
status: | Incomplete → Fix Committed |
- Needs a team bug subscriber for whomever will look after this in Ubuntu, presumably the desktop team opensource- src, ubuntu-geoip, and webkitgtk)
- Can we port all of main during the vivid cycle? I'd really like to not ship two geoclues in main. (remaining main reverse depends on geoclue1 are: empathy, libunity-webapps, qtlocation-
- Tests are disabled, that sucks. But they have seem to have a misleading comment in debian/rules. If I take away the "|| true", the build still runs. And I don't see any tests even being run by a "make check". Maybe there is a different way to run the tests... What's the story there?