Fly together Forever 比翼恒飞

When setuping trac on a server, I encountered a strange issue: the python binding of subversion can not be loaded by python, I got something like this:

libsvn_ra_dav-1.so.0: undefined symbol: gss_delete_sec_context

After googling around, I found out that, someone suggested to disable neon when compiling subversion 1.4. That did do the trick, and binding works. However, with neon disabled, svn can not work with http/https repositories, which is not acceptable. So I have to find another workaround.

Google told me that gss_delete_sec_context is part of libgssapi.so, and "ldd libsvn_ra_dav-1.so.0" reveals that it does not link to any libgssapi.so at all. The obvious workaround is to explicitly specify that in the Makefile.

Edit the top Makefile in subversion 1.4.0, append "-lgssapi" to this line:

SVN_APR_LIBS = ...

(… is the actual content you will see) after installing it, everything works fine now.

It may be argued that this is not a subversion issue, rather than a neon one (it should link to gssapi). As subversion uses a bundled neon, so maybe it is more faire to call it a subversion bug.

After fixing a SJSD svn trunk regression bug reported in the bug tracking system, I tried to make eZ installed in a subdir work with rewrite rules in apache 1.3 (not virtual host setup), as I already achieved it in lighttpd, it must be feasible in apache as well: the mod_rewrite can achieve almost anything as long as you can come up with. (PHP-CGI is used in the apache)

(more…)

Since setup of lighttpd in my test server, it seems working pretty fine. However, without the index.php specified in the url, it does not work. Lighttpd definitely supports rewrite rules, as I see an module named mod_rewrite in lighttpd config file.

After a bit of searching around and failure and trial, I finally got it working.

(more…)

Yesterday, I upgraded the eZ publish setup in SCIM project website from 3.5 to latest stable version 3.8. For your references, here I will present the details about how to achieve this.

Before anything else, first make your eZ offline in case users want to access it. You can achieve this easily by just replace the eZ index.php with a file stating that “the site is undergoing an upgrade and will back online soon” or similar.

(more…)

Since several days ago, whenever I connect to this server via ssh, it freezes very easily. To my impression, it seems that the idle timeout is set to a very short period. However, after checking the sshd_config file, it has not been changed for several months. Confused…

Today, I was working on upgrading the eZ publish in SCIM project from version 3.5.x to 3.8.x. It was really annoying that the ssh froze every now and then: I kept reconnecting/rediring to the working path/re-opening vim to edit the files.

Finally, I decided to face the issue and solve it!

(more…)

After making a patch for eZ to work with lighttpd/fastcgi, I thought it should be also possible to make eZ publish work with Apache CGI mode (I am still using apache1.3.34).

(more…)

It is well known that eZ publish does not play well with CGI, thus it can not work properly with some minority web servers, such as lighttpd and nignx (and I managed to google out an English blog about how to configure nignx) which only support php in CGI mode. However after reading a thread in eZ forum, I wanted to give it a shoot.

First, I have to decid which of the two minority web server I’d like to try. Although personally I prefer the cool name of nignx (pronounced as engine X), it does not support php directly: instead it depends on lighttpd to handle php request. It is obvious I have to go with lighttpd to run eZ.

After some painful googling about howto make lighttpd work with fastcgi/php etc, I finnally managed to work out a way to get through the mess, and make eZ Publish work with CGI as smoothly as in php apache mod.

(more…)