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-ng Relocations: (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/Daemons Source 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 <[log in to unmask]>
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
|
