Bug 1386859 (gcr-rebase) - rebase gcr to 3.20.0
Summary: rebase gcr to 3.20.0
Keywords:
Status: CLOSED ERRATA
Alias: gcr-rebase
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gcr
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Colin Walters
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: gnome-rebase
TreeView+ depends on / blocked
 
Reported: 2016-10-19 17:51 UTC by Matthias Clasen
Modified: 2017-08-01 21:31 UTC (History)
4 users (show)

Fixed In Version: gcr-3.20.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 21:31:15 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:2144 0 normal SHIPPED_LIVE seahorse bug fix update 2017-08-01 18:39:49 UTC

Description Matthias Clasen 2016-10-19 17:51:35 UTC 
This is part of rebasing GNOME to 3.22.
Comment 2 Tomas Pelka 2016-10-31 13:36:06 UTC 
Please review this bz it is needed for planned GNOME 3.22 rebase in RHEL7.4.

Either qa_ACK or let us know immediately that you won't be able to accept this component for 7.4. 

Thanks
-Tom
Comment 4 Karel Srot 2016-11-21 13:25:27 UTC 
typical gcr consumers are seahorse, gnome-keyring, evolution, gnome-shell.
Comment 6 Kalev Lember 2017-02-05 17:52:06 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/gcr/log/?h=private-rhel-7.4-rebase
Comment 7 Kalev Lember 2017-02-09 14:20:31 UTC 
I've now merged the rebase branch and built gcr-3.20.0-1.el7 for the rhel-7.4-gnome build target.
Comment 10 errata-xmlrpc 2017-08-01 21:31:15 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:2144
Note You need to log in before you can comment on or make changes to this bug.