Bug 1107839
Summary: | Consider adding explicit version dependency: Requires: libestr >= 0.1.9 | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Brenton Leanhardt <bleanhar> | |
Component: | rsyslog | Assignee: | Tomas Heinrich <theinric> | |
Status: | CLOSED ERRATA | QA Contact: | Marek Marusic <mmarusic> | |
Severity: | low | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 7.1 | CC: | mmarusic, pvrabec | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1107840 (view as bug list) | Environment: | ||
Last Closed: | 2015-11-19 14:29:47 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: | 1107840 |
Description
Brenton Leanhardt
2014-06-10 18:32:05 UTC
You're probably right, I'll add the dependency in the next update. (In reply to Brenton Leanhardt from comment #0) > The rsyslog package has "BuildRequires: libestr-devel >= 0.1.9". I suspect > the build environment is automatically adding the libestr dependency however > it is not setting the version to match the build requirement. That is correct. This should be, ideally, solved by depending on a specific so-name - rpm would process this dependency transparently and automatically. But upstream doesn't currently version the library interface. > It's likely not strictly required for RHEL 7 however it's nice for distro > maintainers to have the dependency if indeed it's actually required. That > way we can avoid the case of libestr-devel >= 0.1.9 being used at build time > but another version being used at runtime if a particular system is wired up > to the incorrect channels or yum repositories. Well, if the package is build again version X, it should, in good faith, expect the same version in the runtime. If using incorrect channels, even the package that suffices the version requirement may have different contents. 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-2015-2173.html |