On Mon, 2009-11-02 at 16:47 +0100, Peter Östlin wrote:
On Mon, Nov 2, 2009 at 2:59 PM, Peter Östlin <peter.ostlin@op5.com> wrote:
On Fri, Oct 30, 2009 at 4:09 PM, Fegan, Joe <Joe.Fegan@hp.com> wrote:
I don't think yum cares about the names of rpm files - all of the important details, including the target architecture, are embedded in in the file, in the rpm header and yum uses that, regardless of the name of the file.
Joe.
Sure, this is actually what I mean. The arch of the syslog-ng package is set to amd64 (the name does not really matter) and I can't seem to get yum to understand that. Might be possible to solve using yum configuration but as far as I understand yum on a default Fedora or CentOS installation will not find packages with amd64 as arch.
/Peter
To clarify, if I try to install the package using yum localinstall I get:
root@t64-mon-app:~# yum localinstall syslog-ng-3.0.4-1.rhel5.amd64.rpm Loaded plugins: fastestmirror Setting up Local Package Process Examining syslog-ng-3.0.4-1.rhel5.amd64.rpm: syslog-ng-3.0.4-1.rhel5.amd64 Cannot add package syslog-ng-3.0.4-1.rhel5.amd64.rpm to transaction. Not a compatible architecture: amd64
So the problem is that yum do not recognize amd64 as a valid arch and I don't know how to tell yum that amd64 is compatible with x86_64. Installing using rpm works but I would like to be able to use yum since it automatically resolves dependencies.
Hmm.. there are two places in our build system that maps amd64 -> x86_64, and as it seems this one was missing and our testers always used rpm to install packages. We can't produce source rpms as these are generated from our already compiled binaries. -- Bazsi