Here's an example where I deliberately rename an rpm file to a stupid value that is unrelated to its real name or contents. You can see that yum has no problem figuring out the real content of the file and that it's an upgrade for an rpm called mx50-diags that is already on the system. [root@atlas1 ~]# yum list mx50-diags -q Installed Packages mx50-diags.x86_64 3.0.0-7450 installed [root@atlas1 ~]# [root@atlas1 ~]# ls -l *rpm -rw-r--r-- 1 root root 2148776 Oct 30 15:37 mx50-diags-3.0.0-7455.x86_64.rpm [root@atlas1 ~]# [root@atlas1 ~]# mv mx50-diags-3.0.0-7455.x86_64.rpm banana.magoo.rpm [root@atlas1 ~]# [root@atlas1 ~]# ls -l *rpm -rw-r--r-- 1 root root 2148776 Oct 30 15:37 banana.magoo.rpm [root@atlas1 ~]# [root@atlas1 ~]# yum localupdate banana.magoo.rpm Setting up Local Package Process Examining banana.magoo.rpm: mx50-diags-3.0.0-7455.x86_64 Marking banana.magoo.rpm as an update to mx50-diags-3.0.0-7450.x86_64 Resolving Dependencies --> Running transaction check ---> Package mx50-diags.x86_64 0:3.0.0-7455 set to be updated --> Finished Dependency Resolution Dependencies Resolved ===================================================================================== Package Arch Version Repository Size ===================================================================================== Updating: mx50-diags x86_64 3.0.0-7455 banana.magoo.rpm 2.0 M Transaction Summary ===================================================================================== Install 0 Package(s) Update 1 Package(s) Remove 0 Package(s) Total download size: 2.0 M Is this ok [y/N]: n Exiting on user Command Complete! [root@atlas1 ~]# -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Fegan, Joe Sent: 30 October 2009 15:10 To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] syslog-ng open source edition for intel based x86_64 machine 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. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Peter Östlin Sent: 30 October 2009 10:35 To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] syslog-ng open source edition for intel based x86_64 machine On Sat, Oct 10, 2009 at 1:38 PM, Balazs Scheidler <bazsi@balabit.hu> wrote:
On Sun, 2009-10-04 at 20:07 +0530, Jain, Vaibhav (GE Healthcare) wrote:
Hi,
In the balabit site syslog-ng(open source edition) is available only for amd64 and i386 platform. Is it available for intel based x86_64 machine ?
we only have one binary for both amd64 and x86_64. it is named amd64 in our internal build system and would need a lot of work to change that.
Does your build system support creating source rpm's? The main problem with the naming scheme as I understand it is that yum do not like the amd64 arch. So if you could gernerate source rpm's it would be pretty easy to rebuild. Cheers /Peter Östlin ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html