More notes re: (not) working on CentOS 5...
Hello Everybody, After reading the previous thread on CentOS and consulting these instructions: http://www.rho.cc/index.php/linux2/48-misc/48-installing-darwin-calendar-ser... ...I'm getting *nothing*, no output, when I do the 'run' command. No combination of parameters gives me any output. However, I did deviate from the instructions at Rho in this manner: 1. Used Python 2.6.5 instead of 2.5. Python 2.6 includes SQLite (it's no longer a separate download/install)... and the SSL in Python 2.5 does *not* handle certificates properly. The SSL in Python 2.6 is based on OpenSSL which does handle certificates properly. 2. Installed Python under /opt/Python-2.6.5. Replacing the system Python with 2.5 (or 2.6) is fraught with danger and should never be done on a production system. To compensate for this, I edited the shell script named 'python' and corrected the full path for the Python I want to use. 3. Checked-out SVN trunk instead of 4538. Has anyone done analysis to see what's different (and broken) between 4538 and trunk? If I have some time I'll dig into the 'run' script to see if I can get it going, and at least get to the point where I get something running. I'd like to be able to fix whatever's wrong in trunk instead of depending on an older version. Cheers, -JK
Yeah I see ya problem... you didn't follow the instructions! :P Joking aside... I updated the instructions for the later builds here: http://www.rho.cc/index.php/calendar-and-contact-server/59-calendar-setup/10... I've just followed my instructions above to the letter, except as you did I installed python 2.6.5.. Well I got further than you but it failed on installing Zope! :( Removing build directory /home/guy/zope.interface-3.3.0/build... Removing pyc files from /home/guy/zope.interface-3.3.0... Building Zope Interface... Traceback (most recent call last): File "./setup.py", line 86, in <module> **extra) File "/usr/lib/python2.6/distutils/core.py", line 152, in setup dist.run_commands() File "/usr/lib/python2.6/distutils/dist.py", line 975, in run_commands self.run_command(cmd) File "/usr/lib/python2.6/distutils/dist.py", line 995, in run_command cmd_obj.run() File "/usr/lib/python2.6/distutils/command/build.py", line 134, in run self.run_command(cmd_name) File "/usr/lib/python2.6/distutils/cmd.py", line 333, in run_command self.distribution.run_command(command) File "/usr/lib/python2.6/distutils/dist.py", line 995, in run_command cmd_obj.run() File "build/bdist.linux-i686/egg/setuptools/command/build_ext.py", line 46, in run File "/usr/lib/python2.6/distutils/command/build_ext.py", line 340, in run self.build_extensions() File "/usr/lib/python2.6/distutils/command/build_ext.py", line 449, in build_extensions self.build_extension(ext) File "build/bdist.linux-i686/egg/setuptools/command/build_ext.py", line 175, in build_extension File "/usr/lib/python2.6/distutils/command/build_ext.py", line 460, in build_extension ext_path = self.get_ext_fullpath(ext.name) File "/usr/lib/python2.6/distutils/command/build_ext.py", line 637, in get_ext_fullpath filename = self.get_ext_filename(ext_name) File "build/bdist.linux-i686/egg/setuptools/command/build_ext.py", line 85, in get_ext_filename KeyError: '_zope_interface_coptimizations' [guy@DCS-TEST1 CalendarServer]$ My only difference from you is that I did indeed install python, by replace the system one.. I agree about not on production systems, which is why I run virtual systems for testing.. However in pythons case it's all to do with links.. in the /usr/bin/ directory you'll see that the file python actually links to the python2.4 or python2.5 file. You can thus change the system version of python by changing the links. "Yum" is the only application that I've found so far which really doesn't like you upgrading python, and that's a simple fix of editing the top line of yum and referencing python2.4.. I would guess that in your case it's not really finding the python you want it to. Oh and as for the differences... there are lots... biggest of which is the inclusion of contact server. If you want to have a DCS server running quickly from trunk and happen to have a proxmox (pve.proxmox.com) server or other openvz capable server then you can always download and use my image. http://forum.proxmox.com/threads/3548-openVZ-Darwin-Calendar-Server-(DCS)-Re... The posting to the forum provides the simple steps necessary to get this working. Once it's installed... change the passwd for the user "build", login as build and then you can svn update to trunk.. It's not far from trunk as it is, Revision 5265 and trunk is at 5433. Cheers, ---Guy On Apr 01, 2010, at 18:41, Joshua Kramer wrote:
Hello Everybody,
After reading the previous thread on CentOS and consulting these instructions:
http://www.rho.cc/index.php/linux2/48-misc/48-installing-darwin-calendar-ser...
...I'm getting *nothing*, no output, when I do the 'run' command. No combination of parameters gives me any output. However, I did deviate from the instructions at Rho in this manner:
1. Used Python 2.6.5 instead of 2.5. Python 2.6 includes SQLite (it's no longer a separate download/install)... and the SSL in Python 2.5 does *not* handle certificates properly. The SSL in Python 2.6 is based on OpenSSL which does handle certificates properly.
2. Installed Python under /opt/Python-2.6.5. Replacing the system Python with 2.5 (or 2.6) is fraught with danger and should never be done on a production system. To compensate for this, I edited the shell script named 'python' and corrected the full path for the Python I want to use.
3. Checked-out SVN trunk instead of 4538. Has anyone done analysis to see what's different (and broken) between 4538 and trunk?
If I have some time I'll dig into the 'run' script to see if I can get it going, and at least get to the point where I get something running. I'd like to be able to fix whatever's wrong in trunk instead of depending on an older version.
Cheers, -JK
_______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
Joking aside... I updated the instructions for the later builds here: ... Well I got further than you but it failed on installing Zope! :(
Oh, ok, it's Zope-based. Goody! How difficult do you think it'd be to separate this out into its requisite components and go from there? In some cases I like the idea of "run the script and go", but in cases like this where the script installs non-standard major infrastructure items it's counterproductive. For example, if I already have an instance of Zope that is running Plone - and that Zope is installed properly under /opt, using it's own non-standard Python which is also installed properly under /opt, I don't want to install yet another Zope simply for calendarserver. But how easy is that, for CalendarServer? I can dig around scripts to find out but I thought I'd ask to see if there's any precedent for doing that. Cheers, -JK
participants (2)
-
Guy
-
Joshua Kramer