Bug 1038792 - Cloud-init requires dmidecode, which is ExclusiveArch x86
Summary: Cloud-init requires dmidecode, which is ExclusiveArch x86
Keywords:
Status: CLOSED DUPLICATE of bug 1025071
Alias: None
Product: Fedora
Classification: Fedora
Component: cloud-init
Version: 20
Hardware: ppc64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Garrett Holmstrom
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 20:07 UTC by Gustavo Luiz Duarte
Modified: 2014-01-27 17:11 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-09 16:08:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gustavo Luiz Duarte 2013-12-05 20:07:54 UTC
Description of problem:

Cloud-init, which is noarch, requires dmidecode, which is "ExclusiveArch: %{ix86} x86_64 ia64". Could we please remove that dependency for ppc and ppc64?


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

How reproducible:
Always

Steps to Reproduce:
1. yum install cloud-init
2.
3.

Actual results:
Error: Package: cloud-init-0.7.2-7.fc20.noarch (fedora)
           Requires: dmidecode


Expected results:
cloud-init installed.

Comment 1 Garrett Holmstrom 2013-12-07 21:44:30 UTC
How do you propose we do that for a noarch package?

Comment 2 Gustavo Luiz Duarte 2013-12-09 12:39:30 UTC
I suggest doing something like this:

%ifarch %{ix86} x86_64
Requires:       dmidecode
%endif

Comment 3 Gustavo Luiz Duarte 2013-12-09 12:41:31 UTC
Sorry, I left ia64 out. Correcting:

%ifarch %{ix86} x86_64 ia64
Requires:       dmidecode
%endif

Comment 4 Matthew Miller 2013-12-09 16:08:48 UTC
Yeah, but arch is "noarch" so that will not work. Plus, that would then just cause cloud-init to _break_ on other architectures in the situation where it wants to call dmidecode.

What we need to do is have better method for detecting alt data sources (the only place this is used) which does not rely on dmidecode. Which is bug #1025071 already. :)

*** This bug has been marked as a duplicate of bug 1025071 ***


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