yum in 5.4 not seeing some packages
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: [r...@sl5build ~]# yum clean all Loaded plugins: kernel-module Cleaning up Everything [r...@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_642.6.1p1-1.rhel5 local pgsphere.x86_641.1.0-1 local [r...@sl5build ~]# yum clean all Loaded plugins: kernel-module Cleaning up Everything [r...@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
Re: yum in 5.4 not seeing some packages
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:
[r...@sl5build ~]# yum clean all
Loaded plugins: kernel-module
Cleaning up Everything
[r...@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_642.6.1p1-1.rhel5 local
pgsphere.x86_641.1.0-1 local
[r...@sl5build ~]# yum clean all
Loaded plugins: kernel-module
Cleaning up Everything
[r...@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 daw...@fnal.gov (630)840-6468
Fermilab ComputingDivision/LSCS/CSI/USS Group
__
Re: yum in 5.4 not seeing some packages
Troy Dawson wrote:
>
> 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
Hi,
These packages are from the syslog-ng site. The name seems to match
what's inside the package AFAICT (see below).
It looks like our 32-bit Scientific Linux machines, as well as 32- and
64-bit RHEL machines have no problem with these RPMs. It's only the yum
on 64-bit Scientific Linux that's not showing them.
Is there a way to tell yum that 'amd64' is valid?
rpm -qp local-rhel5-x86_64/RPMS/syslog-ng-3.0.4-1.rhel5.amd64.rpm --qf
"==%{name}==%{arch}==\n"
warning: local-rhel5-x86_64/RPMS/syslog-ng-3.0.4-1.rhel5.amd64.rpm:
Header V3 DSA signature: NOKEY, key ID 2aa28252
==syslog-ng==amd64==
rpm -qpi local-rhel5-x86_64/RPMS/syslog-ng-3.0.4-1.rhel5.amd64.rpm
warning: local-rhel5-x86_64/RPMS/syslog-ng-3.0.4-1.rhel5.amd64.rpm:
Header V3 DSA signature: NOKEY, key ID 2aa28252
Name: syslog-ngRelocations: (not
relocatable)
Version : 3.0.4 Vendor: BalaBit IT Ltd.
Release : 1.rhel5 Build Date: Wed 05 Aug 2009
08:53:47 PM CEST
Install Date: (not installed) Build Host: hapci.balabit
Group : System Environment/DaemonsSource RPM:
syslog-ng-3.0.4-1.rhel5.src.rpm
Size: 12939983 License: BalaBit
Proprietary License
Signature : DSA/SHA1, Wed 05 Aug 2009 08:53:55 PM CEST, Key ID
3bdaf86d2aa28252
Packager: Tamas Pal
URL : http://www.balabit.com
Summary : Next generation system logging daemon
Description :
The syslog-ng application is a flexible and highly scalable system
logging tool.
It is often used to manage log messages and implement centralized
logging, where
the aim is to collect the log messages of several devices to a single,
central
log server.
The main features of syslog-ng include:
* Support for the BSD (RFC 3164) and IETF (RFC 5424-5428) syslog
protocol
standards
* Secure log transfer and storage using public-key encryption
* Reliable log transfer using TCP and TLS
* Pattern based message classification
* Direct database access for MSSQL, MySQL, Oracle, PostgreSQL, and
SQLite
* Flow-control
* Message filtering based on the content and properties of messages
* Message rewriting
* IPv4 and IPv6 support
* Ability to handle high message rates
* Support for heterogeneous UNIX environments
For details about syslog-ng, see the syslog-ng homepage at:
http://www.balabit.com/network-security/syslog-ng/
The documentation of syslog-ng at:
http://www.balabit.com/support/documentation/
Questions, feedback, and bug reports are welcome at the syslog-ng
mailing list:
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Re: yum in 5.4 not seeing some packages
Tim, It's interesting that the rpms for the 3.05 version of syslog-ng are correctly named with a "x86_64.rpm" extension. Perhaps you could use those and sidestep this problem? -Ed Tim Edwards wrote: These packages are from the syslog-ng site. The name seems to match what's inside the package AFAICT (see below).
Re: yum in 5.4 not seeing some packages
Ed Brown wrote: > Tim, > > It's interesting that the rpms for the 3.05 version of syslog-ng are > correctly named with a "x86_64.rpm" extension. Perhaps you could use > those and sidestep this problem? > > -Ed Thanks, I didn't notice they'd released that but it fixes the problem. I also checked again and it looks like RHEL5.4 has the same behaviour (ignoring amd64 arch) so I guess there's no fault in SL. Tim
Re: yum in 5.4 not seeing some packages
Tim Edwards wrote: I also checked again and it looks like RHEL5.4 has the same behaviour (ignoring amd64 arch) so I guess there's no fault in SL. I wondered about that. I believe the naming convention for architecture is built into rpm itself, that this would not just be a yum problem. -Ed
