https://bugzilla.redhat.com/show_bug.cgi?id=2058448
Bug ID: 2058448 Summary: rocksdb: rebuild for gflags update in c8s Product: Fedora EPEL Version: epel8 Status: NEW Component: rocksdb Assignee: epel-packagers-sig@lists.fedoraproject.org Reporter: carl@redhat.com CC: dcavalca@fb.com, epel-packagers-sig@lists.fedoraproject.org, hegjon@gmail.com, mmuzila@redhat.com Target Milestone: --- Classification: Fedora
Description of problem: In CentOS Stream 8, the gflags package was updated from 2.1.2-6.el8 to 2.2.2-1.el8 (see bug 2035143). That introduces an soname bump from libgflags.so.2.1 to libgflags.so.2.2. rocksdb links against that soname and must be rebuilt in epel8-next to work correctly on c8s.
Version-Release number of selected component (if applicable): rocksdb-6.26.1-2.el8
Steps to Reproduce: 1. dnf install rocksdb (this resolves to the older gflags in the repo) 2. dnf update gflags
Actual results: Error: Problem: problem with installed package rocksdb-6.26.1-2.el8.x86_64 - package rocksdb-6.26.1-2.el8.x86_64 requires libgflags.so.2.1()(64bit), but none of the providers can be installed - cannot install both gflags-2.2.2-1.el8.x86_64 and gflags-2.1.2-6.el8.x86_64 - cannot install the best update candidate for package gflags-2.1.2-6.el8.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Expected results: installation of the latest gflags and rocksdb
Additional info: This is happening in c8s now, but will also happen when RHEL 8.6 is released. At that point it can be remediated in regular epel8.
https://bugzilla.redhat.com/show_bug.cgi?id=2058448
Carl George 🤠 carl@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|epel-packagers-sig@lists.fe |carl@redhat.com |doraproject.org |
https://bugzilla.redhat.com/show_bug.cgi?id=2058448
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED
--- Comment #1 from Fedora Update System updates@fedoraproject.org --- FEDORA-EPEL-NEXT-2022-06d6495d37 has been submitted as an update to Fedora EPEL 8 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-06d6495d37
https://bugzilla.redhat.com/show_bug.cgi?id=2058448
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA
--- Comment #2 from Fedora Update System updates@fedoraproject.org --- FEDORA-EPEL-NEXT-2022-06d6495d37 has been pushed to the Fedora EPEL 8 Next testing repository.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-06d6495d37
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
https://bugzilla.redhat.com/show_bug.cgi?id=2058448
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Fixed In Version| |rocksdb-6.26.1-2.el8.next Resolution|--- |ERRATA Last Closed| |2022-03-05 17:58:57
--- Comment #3 from Fedora Update System updates@fedoraproject.org --- FEDORA-EPEL-NEXT-2022-06d6495d37 has been pushed to the Fedora EPEL 8 Next stable repository. If problem still persists, please make note of it in this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=2058448
Carl George 🤠 carl@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|ERRATA |--- Status|CLOSED |MODIFIED Keywords| |Reopened
--- Comment #4 from Carl George 🤠 carl@redhat.com --- The gflags update was reverted before RHEL 8.6 [0], and is now getting reverted in c8s as well [1]. Users with rocksdb-6.26.1-2.el8.next will need an upgrade path to get back onto a build that links against libgflags.so.2.1. I'm doing a release bump rebuild in epel8 to address this.
[0] bug 2035143 comment 20 [1] bug 2035143 comment 27
https://bugzilla.redhat.com/show_bug.cgi?id=2058448
--- Comment #5 from Fedora Update System updates@fedoraproject.org --- FEDORA-EPEL-2022-6fa9fb5922 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6fa9fb5922
https://bugzilla.redhat.com/show_bug.cgi?id=2058448
Fedora Update System updates@fedoraproject.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed In Version|rocksdb-6.26.1-2.el8.next |rocksdb-6.26.1-2.el8.next | |rocksdb-6.26.1-3.el8 Resolution|--- |ERRATA Status|MODIFIED |CLOSED Last Closed|2022-03-05 17:58:57 |2022-05-14 03:03:32
--- Comment #6 from Fedora Update System updates@fedoraproject.org --- FEDORA-EPEL-2022-6fa9fb5922 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
epel-packagers-sig@lists.fedoraproject.org
-
bugzilla＠redhat.com