Commented by: @pmakowski

Don't use this rpm
if you want rpm use the one from the EPEL repository for Centos or RHEL (http://fedoraproject.org/wiki/EPEL),
or use the tar.gz package
Rpm provided on sourceforge by Firebird project are too generic, don't follow all distro rules, and don't support updates

Commented by: Eberhard Leba (eleba)

Philippe
thanks for the hint.
I will give it a try :)
To be honest I found that using RPM search as well, but I did not know how "reliable" the source is.
So it might just be a documentation issue to point to EPEL project as an alternative source for RHEL/CENTOS RPMS.

regards Eberhard

Commented by: @AlexPeshkoff

We historically provided a kind of 'universal' rpm package on SF, supposed to work on different OS's. But ability to have something working and universal is currently close to unreal - when library names used a s dependencies are same for all distros, packages will be called differently. BTW, earlier there were no problems using library name as dependency name. Moreover, it was documented.

Therefore since FB3 we stop providing rpms at SF. If one needs rpm instead tar.gz he should really better use distro-specific sources.

Commented by: Eberhard Leba (eleba)

Unfortunately the EPEL package is also inconsistent.
it requires lots of other Firebird packages to be installed:

firebird-superserver-2.5.1.26351.0-1.el6.x86_64.rpm depends on
* firebird = 2.5.1.26351.0-1.el6
and
> firebird-libfbclient-2.5.1.26351.0-1.el6.x86_64.rpm

firebird-2.5.1.26351.0-1.el6.x86_64.rpm in turn requires
* firebird-arch = 2.5.1.26351.0-1.el6 ---> not available on EPEL
* firebird-filesystem
* libfbembed.so.2.5()(64bit)

So the user is left alone with this mess because of the WONT FIX. :(

PS: I know this is the wrong place to complain about a bug in EPEL packages. This is just to show the consequences.

So whats left is the old fashioned and outdated tar install.

Commented by: @pmakowski

yum install firebird firebird-superserver

should do all it need

and no it is not a mess
just that this way, you can setup client only for example, or dev only, etc, more flexibility, and every pieces at the right place according to the distro rule, not all in /opt

but you have the choice

and yes, if you find a bug with Epel package, report it there :
https://bugzilla.redhat.com

Commented by: Eberhard Leba (eleba)

So I created a file /etc/yum.repos.d/epel.repo with the following content::
[EPEL64]
name=Extra Packages for Enterprise Linux x86_64
baseurl=http://dl\.fedoraproject\.org/pub/epel/6/x86\_64/
gpgkey=http://dl\.fedoraproject\.org/pub/epel/RPM\-GPG\-KEY\-EPEL\-6

ran the command

yum install firebird firebird-superserver

AND ---- MAGIC ----

it installed.

Philippe Thanks allot.!