Bug 1386841
| Summary: | rebase dconf to 0.26.0 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Matthias Clasen <mclasen> |
| Component: | dconf | Assignee: | Marek Kašík <mkasik> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | unspecified | Docs Contact: | Mirek Jahoda <mjahoda> |
| Priority: | medium | ||
| Version: | 7.4 | CC: | tpelka |
| Target Milestone: | rc | Keywords: | Rebase |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 09:35:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1386874 | ||
| Bug Blocks: | 1383353, 1388931 | ||
|
Description
Matthias Clasen
2016-10-19 17:10:14 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. 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 |