Bug 1386841 - rebase dconf to 0.26.0
Summary: rebase dconf to 0.26.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dconf
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Marek Kašík
QA Contact: Desktop QE
Mirek Jahoda
URL:
Whiteboard:
Depends On: glib2-rebase
Blocks: gnome-rebase 1388931
TreeView+ depends on / blocked
 
Reported: 2016-10-19 17:10 UTC by Matthias Clasen
Modified: 2017-08-01 09:35 UTC (History)
1 user (show)

Fixed In Version: dconf-0.26.0-1.el7
Doc Type: Deprecated Functionality
Doc Text:
dconf-dbus-1 API was removed in dconf 0.26.0. However, the library itself was backported to preserve binary compatibility. You should use GDBus instead of dconf-dbus-1 since dconf 0.26.0. dconf-error.h was renamed to dconf-enums.h. dconf-editor was split off dconf to separate package named dconf-editor.
Clone Of:
Environment:
Last Closed: 2017-08-01 09:35:54 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2302 0 normal SHIPPED_LIVE dconf bug fix and enhancement update 2017-08-01 12:41:13 UTC

Description Matthias Clasen 2016-10-19 17:10:14 UTC 
This is part of rebasing GNOME to 3.22.
Comment 2 Marek Kašík 2016-10-26 13:18:45 UTC 
Rebase of DConf will need new package 'dconf-editor' because 'dconf-editor' was split out of dconf before 0.24.0.

We will also need to backport dconf-dbus-1 library back because it was removed. I'll backport it but without header files, just for compatibility reason. Newly written code should use GDBus (btw, no package from RHEL7 repository requires this library now).

There was also a rename of 'dconf-error.h' header file to 'dconf-enums.h' so we can consider this as an API change.

Since dconf 0.26.0 needs at least glib2-2.44.0 I've set dependency on the rebase of glib2 to 2.50.x.
Comment 5 errata-xmlrpc 2017-08-01 09:35:54 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://access.redhat.com/errata/RHBA-2017:2302
Note You need to log in before you can comment on or make changes to this bug.