Bug 595689 - attr should depend on the same version of libattr
attr should depend on the same version of libattr
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: attr (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Kamil Dudka
Miroslav Vadkerti
Depends On:
Blocks: 593740
  Show dependency treegraph
Reported: 2010-05-25 07:40 EDT by Kamil Dudka
Modified: 2010-07-02 14:51 EDT (History)
2 users (show)

See Also:
Fixed In Version: attr-2.4.44-3.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-02 14:51:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kamil Dudka 2010-05-25 07:40:17 EDT
Description of problem:
The dependency is missing.

Version-Release number of selected component (if applicable):

Additional info:
The same problem in rawhide.
Comment 1 RHEL Product and Program Management 2010-05-25 07:56:09 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 2 Kamil Dudka 2010-05-25 08:05:08 EDT
fixed in rawhide and built as attr-2.4.44-5.fc14
Comment 3 Kamil Dudka 2010-05-25 11:09:39 EDT
how to check:

$ rpm -q attr --requires | grep libattr' '
Comment 4 Kamil Dudka 2010-05-25 13:10:07 EDT
built as attr-2.4.44-3.el6
Comment 6 Miroslav Vadkerti 2010-06-04 08:58:10 EDT
VERIFIED as fixed in attr-2.4.44-3.el6

[root@pogolinux-2 ~]# rpm -q attr
[root@pogolinux-2 ~]# rpm -q attr --requires | grep libattr' ' 
libattr = 2.4.44-3.el6
Comment 7 releng-rhel@redhat.com 2010-07-02 14:51:24 EDT
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.