RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1221940 - Obsolete geoclue1
Summary: Obsolete geoclue1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: geoclue2
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Zeeshan Ali
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1091355
TreeView+ depends on / blocked
 
Reported: 2015-05-15 10:01 UTC by Bastien Nocera
Modified: 2016-09-20 01:43 UTC (History)
2 users (show)

Fixed In Version: geoclue2-2.1.10-4.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 08:28:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2157 0 normal SHIPPED_LIVE control-center bug fix and enhancement update 2015-11-19 08:48:59 UTC

Description Bastien Nocera 2015-05-15 10:01:38 UTC 
geoclue1 is completely dead upstream for a couple of years.

We should add Obsoletes for geoclue1 to geoclue2, and block geoclue1 from the distribution.

Was geoclue1 ever a supported API for customer applications?
Comment 2 Zeeshan Ali 2015-07-14 15:04:37 UTC 
Sure, shall we obsolete all geoclue1 packages?

geoclue
geoclue-gui
python-geoclue
geoclue-gypsy
geoclue-gsmloc
geoclue-devel
geoclue-doc

Last two should be obsoleted by geoclue2-devel I guess.
Comment 3 Zeeshan Ali 2015-07-14 17:32:54 UTC 
I just went for a simple fix for now: Added Obsoletes on geoclue
Comment 4 Bastien Nocera 2015-07-15 06:00:54 UTC 
This isn't good enough. Obsoletes *must* be versioned.

You should also obsolete all the Geoclue1 sub-packages that could have been installed, otherwise from:

geoclue
geoclue-gui (which requires geoclue of the same version)

You'd try to upgrade to:
geoclue2 (which obsoletes geoclue)
but geoclue-gui would require geoclue to be installed, not geoclue2
which would break the upgrade.
Comment 8 errata-xmlrpc 2015-11-19 08:28:18 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2157.html
Comment 9 Zeeshan Ali 2016-04-27 14:21:42 UTC 
(In reply to Bastien Nocera from comment #0)
> geoclue1 is completely dead upstream for a couple of years.
> 
> We should add Obsoletes for geoclue1 to geoclue2, and block geoclue1 from
> the distribution.
> 
> Was geoclue1 ever a supported API for customer applications?

Apparently it is in EPEL at least: https://bugzilla.redhat.com/show_bug.cgi?id=1285479
Note You need to log in before you can comment on or make changes to this bug.