Bug 230893 - Broken dependency in dmraid-1.0.0.rc14-1_RHEL4_U5
Broken dependency in dmraid-1.0.0.rc14-1_RHEL4_U5
Status: CLOSED DUPLICATE of bug 229267
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: dmraid (Show other bugs)
4.5
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: LVM and device-mapper development team
Corey Marthaler
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-04 06:06 EST by Suzuki Takashi
Modified: 2007-11-30 17:07 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-04 07:54:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Suzuki Takashi 2007-03-04 06:06:58 EST
Description of problem:
dmraid-1.0.0.rc14-1_RHEL4_U5 requires a kpartx package,
which is missing from the RHEL4.5 beta channel.

Version-Release number of selected component (if applicable):
dmraid-1.0.0.rc14-1_RHEL4_U5

How reproducible:
Always.

Steps to Reproduce:
1. Get dmraid-1.0.0.rc14-1_RHEL4_U5.i386.rpm from RHN.
2. rpm -Uvh dmraid-1.0.0.rc14-1_RHEL4_U5.i386.rpm.
  
Actual results:
rpm complains and refuses to update:
error: Failed dependencies:
        kpartx is needed by dmraid-1.0.0.rc14-1_RHEL4_U5.i386

Expected results:
Updated successfully.

Additional info:
If you upgrade systems with a dmraid package using up2date, 
up2date will refuse to update, as it cannot resolve part of the dependencies.
Comment 1 Heinz Mauelshagen 2007-03-04 07:54:13 EST

*** This bug has been marked as a duplicate of 229267 ***
Comment 2 Suzuki Takashi 2007-03-04 08:20:34 EST
At least I cannot access the bug 229267.
Is the information there available to all the beta testers, already or somewhere
else?
Comment 3 Heinz Mauelshagen 2007-03-05 05:08:14 EST
Opened up 229267 for Beta program members.

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