Bug 2055222

Summary: glog-0.3.5-4.el8 not compatible with gflags-2.2.2-1.el8
Product: Red Hat Enterprise Linux 8 Reporter: Alex Iribarren <alex.iribarren>
Component: glogAssignee: Jiri Kucera <jkucera>
Status: CLOSED CURRENTRELEASE QA Contact: rhel8-maint
Severity: high Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, djuarezg, jwboyer, ovasik, steve.traylen
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glog-0.3.5-4.el8.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-30 08:26:09 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 Alex Iribarren 2022-02-16 13:45:25 UTC
gflags was recently upgraded (Bug 2035143) to gflags-2.2.2-1.el8 and now provides libgflags.so.2.2()(64bit).

glog-0.3.5-4.el8 was also rebuilt but it still requires libgflags.so.2.1()(64bit).

Running `dnf install glog gflags` currently fails because of this conflict.

Comment 1 Alex Iribarren 2022-02-24 15:55:03 UTC
Do you have any updates on this?

Comment 2 Alex Iribarren 2022-02-25 13:55:45 UTC
It seems glog-0.3.5-4.el8.0.1 was released yesterday and it fixes the problem. Thanks for fixing it, but it would have been nice to get some feedback via the ticket.

Comment 3 Jiri Kucera 2022-02-27 22:23:54 UTC
Alex, sorry for the delayed reaction. Please, use the Bugzilla's needinfo feature if you need to be sure your request is noticed at time. It sends a reminder every 24 hours. Because of approaching various deadlines set to the end of the month, people are receiving hundreds of emails per day for the last 4-5 weeks from Bugzilla and other tools and sometimes it happens that some notifications stay unnoticed for some period of time (even email filtering sometimes does not help).