Bug 1312201
Summary: | [SPEC] systemd should require glib2 ? | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Ashish Shah <ashishks> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED ERRATA | QA Contact: | Branislav Blaškovič <bblaskov> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.2 | CC: | ayadav, bblaskov, jscotka, lnykryn, masanari.iida, msekleta, systemd-maint-list, vchoudha |
Target Milestone: | rc | Keywords: | EasyFix, Regression, Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | systemd-219-21.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 00:52:24 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1289485 |
Description
Ashish Shah
2016-02-26 05:14:13 UTC
If I am not mistaken this is a glib problem. They have changed the api without bumping soname. And the dependencies on libraries are added automatically, they should not be in spec. Lukáš, at the moment the burden is on dependent packages to bump the Requires. See https://bugzilla.redhat.com/show_bug.cgi?id=300241 and many others. GLib doesn't use versioned symbols, so dependent packages have to manually increase the Requires:. I know it sucks, and RPM could handle this better, but it is the way it is. It's not a matter of soname bumping as no ABI broke, it was just added. So, optionally please do consider editing the systemd spec file to use >= 2.42. Ok, lets add that in our spec. I have encountered the same problem. Add me in CC # rpm -q libgudev1 libgudev1-219-22.el7 # rpm --requires -q libgudev1 | grep glib2 glib2 >= 2.42 libgudev1 now requires glib2 of version 2.42 and higher. Marking as verified. 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-2216.html |