SCIENTIFIC-LINUX-DEVEL Archives

August 2005

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Maillling list for Scientific Linux developers worldwide <[log in to unmask]>
Date:
Tue, 9 Aug 2005 10:57:02 -0500
MIME-version:
1.0
Reply-To:
Connie Sieh <[log in to unmask]>
Content-type:
TEXT/PLAIN; charset=US-ASCII
Subject:
Re: comps.rpm for i386 is x86_64
From:
Connie Sieh <[log in to unmask]>
In-Reply-To:
<[log in to unmask]>
Comments:
To: Gerald Teschl <[log in to unmask]> cc: [log in to unmask]
Parts/Attachments:
TEXT/PLAIN (28 lines) 
Gerald,

On Tue, 9 Aug 2005, Gerald Teschl wrote:

> By looking for grub errors I noticed some anaconda errors indicating that
> comps.rpm has the wrong arch. In fact:
> 
> # rpm -qp --qf "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}.rpm\n" comps.rpm
> comps-41-0.20050727.x86_64.rpm

Thats what happens when you build both x86_64 and i386 on the same system.  
I have since added checks to my build scripts.

> 
> Shouldn't it be "noarch"?

It should be i386.  Not that anything in there is either i386 or x86_64 
but that is they way it comes from the upstream vendor.

> 
> Gerald
> 

Thanks for telling me about this.  Now have to decide what to do about it 
as comps.rpm is not really that exciting.

-Connie Sieh

ATOM RSS1 RSS2