Bug 1305515
| Summary: | Rebase to >= 2.46 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Colin Walters <walters> |
| Component: | glib2 | Assignee: | Colin Walters <walters> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | mclasen, mcrha, tpelka, vbenes, walters |
| Target Milestone: | rc | Keywords: | Rebase |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glib2-2.46.2-2.el7 | Doc Type: | Rebase: Bug Fixes and Enhancements |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-04 01:39:45 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: | |||
|
Description
Colin Walters
2016-02-08 13:21:19 UTC
Matthias, can you help me acquire a qa_ack? We have 2.42.2 in rhel7, Colin could you please sum up or link to list of changes compared to targeted 2.46? Or hints what to focus on. Should we expect libhif rebase too? (In reply to Tomas Pelka from comment #3) > We have 2.42.2 in rhel7, Colin could you please sum up or link to list of > changes compared to targeted 2.46? Or hints what to focus on. The NEWS file has the usuals: https://git.gnome.org/browse/glib/tree/NEWS Broadly speaking I don't think there's anything really risky. > Should we expect libhif rebase too? Probably, but you'd have to ask Richard for sure. rpm-ostree (as used by Atomic Host) will carry a private copy. This change forgot of the issue in the evolution-data-server, filled upstream as this bug [1]. I'm building evolution-data-server-3.12.11-28.el7 with the upstream fix included. [1] https://bugzilla.gnome.org/show_bug.cgi?id=755075 *** Bug 1324837 has been marked as a duplicate of this bug. *** 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-2016-2257.html |