Tim Edwards wrote:
> Hi,
> 
> I have a local repository setup with 8 packages in it. On our Scientific
> Linux 5.1,5.2 or 5.3 (or RHEL5 of all versions) it works fine. However
> on our only SL5.4 x86_64 machine yum seems to only be capable of seeing
> 5 of the RPMs.
> 
> Here is me trying to see the packages, note the initial output from yum
> list all (at the bottom) which shows that it sees all 8 packages:
> 
> [root@sl5build ~]# yum clean all
> Loaded plugins: kernel-module
> Cleaning up Everything
> [root@sl5build ~]# yum list all | grep local
> MySQL-client-community.x86_64              5.1.40-0.rhel5              local
> MySQL-server-community.x86_64              5.1.40-0.rhel5              local
> amanda-backup_server.x86_64                2.6.1p1-1.rhel5             local
> pgsphere.x86_64                            1.1.0-1                     local
> [root@sl5build ~]# yum clean all
> Loaded plugins: kernel-module
> Cleaning up Everything
> [root@sl5build ~]# yum list all
> Loaded plugins: kernel-module
> local                                                    |  951 B     00:00
> local/primary                                            | 5.9 kB     00:00
> local
>     8/8
> 
> 
> Here are the files that are in the repository:
> ls local-rhel5-x86_64/RPMS/
> amanda-backup_client-2.6.1p1-1.rhel5.x86_64.rpm
> amanda-backup_server-2.6.1p1-1.rhel5.x86_64.rpm
> MySQL-client-community-5.1.40-0.rhel5.x86_64.rpm
> MySQL-server-community-5.1.40-0.rhel5.x86_64.rpm
> nagios-eso-plugins-1.2-14.x86_64.rpm
> pgsphere-1.1.0-1.x86_64.rpm
> repodata
> syslog-ng-3.0.4-1.rhel5.amd64.rpm
> syslog-ng-client-3.0.4-1.rhel5.amd64.rpm
> 
> The only difference I can see is that these files are named .amd64.rpm
> instead of .x86_64.rpm - is this a yum bug that it's refusing to look at
> these files?
> 
> THanks
> 
> Tim Edwards

Hi Tim,
I would suspect any package that is labeled *amd64.rpm

I know in the past, yum doesn't like it when the rpm file name doesn't 
match the data that is inside the rpm.  I believe this is a security 
option and not a bug.  You don't want someone slipping in a package 
called foo.rpm, that is really a hacked up bar.rpm.

I would do a rpm query on those packages, and if need be, rename them to 
what they properly are.

rpm -qpi syslog-ng-3.0.4-1.rhel5.amd64.rpm
rpm -qp syslog-ng-3.0.4-1.rhel5.amd64.rpm --qf "==%{name}==%{arch}==\n"

Troy
-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/LSCS/CSI/USS Group
__________________________________________________