(Migrated) RPM package repository for Fedora

(This message has been automatically imported from the retired mailing list)

Hi,

I’ve succeeded in running Zato-1.1 on Fedora 20 when starting from CentOS
yum repositories provided (
https://zato.io/docs/admin/guide/install-rhel.html).

The flight was not quite normal, since there are some differences in Fedora
20 and the RPMs compiled for CentOS 6. The most notable differences are:

  1. /opt/zato/1.1/zato_extra_paths symlinks are referring to
    /usr/lib/python2.6
    and latest Fedoras use Python 2.7 already. This issue revealed itself with
    zato --version check.
  2. zato RPM (gevent-0.13.8) is compiled against libevent-1.4, but Fedora
    20 has libevent-2.0, thus I had to rebuild buildout, this made me install
    extra gcc, libevent-devel and libyaml-devel. This issue it was difficult
    to reveal, since there was nothing in the logs and I’ve had to dig as deep
    as attempt running server with “/opt/zato/1.1/bin/py -m zato.server.main
    path/to/server1” command. Some better server startup issue surfacing (some
    traceback in logs) would be helpful.

I do not know if there are any other issues, but even this way Zato RPM
installation looks promising. Thank you for all your work. BTW, is there
zato .src.rpm anywhere or git repository with .spec file and other
prerequisites to rebuild package?

Regards,

Myroslav Opyr

On 04/24/2014 12:48 PM, Myroslav Opyr wrote:

Hi Myroslav, many thanks for confirming it!

  1. zato RPM (gevent-0.13.8) is compiled against libevent-1.4, but Fedora
    20 has libevent-2.0, thus I had to rebuild buildout, this made me install
    extra gcc, libevent-devel and libyaml-devel. This issue it was difficult
    to reveal, since there was nothing in the logs and I’ve had to dig as deep
    as attempt running server with “/opt/zato/1.1/bin/py -m zato.server.main
    path/to/server1” command. Some better server startup issue surfacing (some
    traceback in logs) would be helpful.

Yes, the plan is to do away with zdaemon. Apparently users are either
okay with restarting a server when something goes wrong or servers run
under Docker so they are spun up anyway - zdaemon is not that helpful as
I was thinking it would be.

I do not know if there are any other issues, but even this way Zato RPM
installation looks promising. Thank you for all your work. BTW, is there
zato .src.rpm anywhere or git repository with .spec file and other
prerequisites to rebuild package?

The .spec is on GH over here

https://github.com/zatosource/zato-build/blob/master/rhel/package-base/zato.spec

I’m currently working on making the build script as convenient to use as
the Debian/Ubuntu one …

https://mailman-mail5.webfaction.com/pipermail/zato-discuss/2014-April/000372.html

… but the process is way more time-consuming given that it includes
compiling Python from scratch each time.

I’ll post a message to the list once it’s ready.

thanks,

On 04/24/2014 12:48 PM, Myroslav Opyr wrote:

Hi Myroslav, many thanks for confirming it!

  1. zato RPM (gevent-0.13.8) is compiled against libevent-1.4, but Fedora
    20 has libevent-2.0, thus I had to rebuild buildout, this made me install
    extra gcc, libevent-devel and libyaml-devel. This issue it was difficult
    to reveal, since there was nothing in the logs and I’ve had to dig as deep
    as attempt running server with “/opt/zato/1.1/bin/py -m zato.server.main
    path/to/server1” command. Some better server startup issue surfacing (some
    traceback in logs) would be helpful.

Yes, the plan is to do away with zdaemon. Apparently users are either
okay with restarting a server when something goes wrong or servers run
under Docker so they are spun up anyway - zdaemon is not that helpful as
I was thinking it would be.

I do not know if there are any other issues, but even this way Zato RPM
installation looks promising. Thank you for all your work. BTW, is there
zato .src.rpm anywhere or git repository with .spec file and other
prerequisites to rebuild package?

The .spec is on GH over here

https://github.com/zatosource/zato-build/blob/master/rhel/package-base/zato.spec

I’m currently working on making the build script as convenient to use as
the Debian/Ubuntu one …

https://mailman-mail5.webfaction.com/pipermail/zato-discuss/2014-April/000372.html

… but the process is way more time-consuming given that it includes
compiling Python from scratch each time.

I’ll post a message to the list once it’s ready.

thanks,