RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1722245 - bump version for glib2
Summary: bump version for glib2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glib2
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.7
Assignee: Colin Walters
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-19 19:17 UTC by Tomas Pelka
Modified: 2019-08-06 12:38 UTC (History)
3 users (show)

Fixed In Version: glib2-2.56.1-5.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 12:38:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2044 0 None None None 2019-08-06 12:38:52 UTC

Description Tomas Pelka 2019-06-19 19:17:17 UTC 
Description of problem:
please bump the el7 glib2 version, as we already released glib2-2.56.1-4.el7_6 in 7.6.z but still have glib2-2.56.1-4.el7 in 7.7, this coincidence break update path 7.6->7.7

Version-Release number of selected component (if applicable):
glib2-2.56.1-4.el7

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
package glib2-2.56.1-4.el7_6.x86_64 (which is newer than glib2-2.56.1-4.el7.x86_64) is already installed
package glib2-2.56.1-4.el7_6.i686 (which is newer than glib2-2.56.1-4.el7.x86_64) is already installed
package glib2-devel-2.56.1-4.el7_6.x86_64 (which is newer than glib2-devel-2.56.1-4.el7.x86_64) is already installed
package glib2-devel-2.56.1-4.el7_6.i686 (which is newer than glib2-devel-2.56.1-4.el7.x86_64) is already installed
package glib2-static-2.56.1-4.el7_6.x86_64 (which is newer than glib2-static-2.56.1-4.el7.i686) is already installed
package glib2-static-2.56.1-4.el7_6.i686 (which is newer than glib2-static-2.56.1-4.el7.i686) is already installed
package glib2-static-2.56.1-4.el7_6.x86_64 (which is newer than glib2-static-2.56.1-4.el7.x86_64) is already installed
package glib2-static-2.56.1-4.el7_6.i686 (which is newer than glib2-static-2.56.1-4.el7.x86_64) is already installed
package glib2-fam-2.56.1-4.el7_6.x86_64 (which is newer than glib2-fam-2.56.1-4.el7.x86_64) is already installed
package glib2-doc-2.56.1-4.el7_6.noarch (which is newer than glib2-doc-2.56.1-4.el7.noarch) is already installed
package glib2-tests-2.56.1-4.el7_6.x86_64 (which is newer than glib2-tests-2.56.1-4.el7.x86_64) is already installed
package glib2-debuginfo-2.56.1-4.el7_6.x86_64 (which is newer than glib2-debuginfo-2.56.1-4.el7.x86_64) is already installed
package glib2-2.56.1-4.el7_6.x86_64 (which is newer than glib2-2.56.1-4.el7.i686) is already installed
package glib2-2.56.1-4.el7_6.i686 (which is newer than glib2-2.56.1-4.el7.i686) is already installed
package glib2-devel-2.56.1-4.el7_6.x86_64 (which is newer than glib2-devel-2.56.1-4.el7.i686) is already installed
package glib2-devel-2.56.1-4.el7_6.i686 (which is newer than glib2-devel-2.56.1-4.el7.i686) is already installed

Expected results:


Additional info:
Comment 1 Ray Strode [halfline] 2019-06-19 20:03:45 UTC 
i'm not sure this is strictly necessary. We can do it if it fixes an upgrade test or something, but both builds should be interchangeable. they have equivalent content.
Comment 2 Ray Strode [halfline] 2019-06-19 20:04:11 UTC 
(midair collision with walters)
Comment 3 Tomas Pelka 2019-06-19 20:22:59 UTC 
(In reply to Ray Strode [halfline] from comment #1)
> i'm not sure this is strictly necessary. We can do it if it fixes an upgrade
> test or something, but both builds should be interchangeable. they have
> equivalent content.

It is not about non-interchange changes, versions and patches are ok.
I believe it is not only about the test is self, but if "already newer pkg" as rpm think is installed the yum update will fail. I can try tomorrow.
Comment 4 Ray Strode [halfline] 2019-06-19 20:56:52 UTC 
fwiw, i'm pretty sure we've allowed this kind of version skew in the past. see example 2 from https://mojo.redhat.com/docs/DOC-1001180 .  bar-2.4-4.el5 is built on the newest branch and bar-2.4-4.el5_8 is built on the z-stream.  this was okay because the developer did a git merge, so both builds had the same content.
Comment 5 Tomas Pelka 2019-06-20 07:50:25 UTC 
OK you are right (as always) yum seems to simply skip glib2-2.56.1-4.el7 so the only one complaining is rpm. So now there is a question whether we still want to fix, on the other hand its something that is almost zero effort.
Comment 12 errata-xmlrpc 2019-08-06 12:38:48 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-2019:2044
Note You need to log in before you can comment on or make changes to this bug.