Mike Schmidt wrote:
I encountered the same problem (no linking common.conf to node.conf) in my last update, which was from the cvs last friday (Oct 22). It took me a while to understand why suddenly the server wouldn't start, but with the help of trusty ol grep, I finally figured out that I had to correct the link. That's in my own build process now.
Is the patch you mentioned in openca_0_9_2_0?
No, openca_0_9_2_0 is a symbolic tag on the openca_0_9_2 branch which marks the last release 0.9.2.0. The patch is on the openca_0_9_2 branch. So you have to checkout openca_0_9_2 to get the production version with the patch.
cvs checkout -P -r openca_0_9_2 openca-0.9
I think we will publish (tag) 0.9.2.1 this week. I will wait for tomorrows list traffic and then we can release.
Michael -- _______________________________________________________________
Michael Bell Humboldt-Universitaet zu Berlin
Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Openca-Users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-users
