Bug 1386977 (gsettings-desktop-schemas-rebase) - rebase gsettings-desktop-schemas to 3.22.x
Summary: rebase gsettings-desktop-schemas to 3.22.x
Keywords:
Status: CLOSED ERRATA
Alias: gsettings-desktop-schemas-rebase
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gsettings-desktop-schemas
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bastien Nocera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: gnome-rebase
TreeView+ depends on / blocked
 
Reported: 2016-10-19 23:56 UTC by Matthias Clasen
Modified: 2017-08-01 22:38 UTC (History)
3 users (show)

Fixed In Version: gsettings-desktop-schemas-3.22.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 22:38:29 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2096 0 normal SHIPPED_LIVE control-center, accountsservice, gnome-settings-daemon, libgnomekbd update 2017-08-01 19:36:13 UTC

Description Matthias Clasen 2016-10-19 23:56:57 UTC
This is part of rebasing GNOME to 3.22

Current release: 3.22.0

Comment 2 Kalev Lember 2017-01-17 14:53:53 UTC
I've pushed a WIP branch with initial rebase work. Package maintainers, please look over the branch and fix up anything if needed:

http://pkgs.devel.redhat.com/cgit/rpms/gsettings-desktop-schemas/log/?h=private-rhel-7.4-rebase

Comment 3 Kalev Lember 2017-02-08 08:06:31 UTC
I've now merged the rebase branch and built gsettings-desktop-schemas-3.22.0-1.el7 for the rhel-7.4-gnome build target.

Comment 5 errata-xmlrpc 2017-08-01 22:38:29 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:2096


Note You need to log in before you can comment on or make changes to this bug.