Question

I am getting a ci error as shown below when trying to save Preferences or WebNotify:

Error saving topic During save of WebNotify an error was found by the version control system. Please notify your TWiki administrator. =/usr/bin/ci -x,v -q -m%COMMENT|U% -t-none -w%USERNAME|S% -u %FILENAME|F% of /twiki/data/Sandbox/WebNotify.txt failed: =

When I create a new topic or save a new topic I do not see the error. I ran configure it it has three warnings that I can't get rid of as shown below:

1. patch Warning: 'patch' program was not found on the current PATH. 2. Warning: Unable to set locale to 'en_US.ISO-8859-1'. The actual locale is 'C' - please test your locale settings. This warning can be ignored if you are not planning to use locales (e.g. your site uses English only) - or you can set {Site}{Locale} to C, which should always work. 3. Warning: Using Perl on Windows, which may have missing or incorrect locales (in Cygwin or ActiveState Perl, respectively) - turning off {Site}{LocaleRegexes} is recommended unless you know your version of Perl has working locale support.

I have repeatedly checked to ensure the owner on all Twiki direcories and files is SYSTEM. Thanks in advance.

Environment

-- TimHayes - 13 Feb 2006

Answer

If you answer a question - or have a question you asked answered by someone - please remember to edit the page and set the status to answered. The status is in a drop-down list below the edit box.

I was having this problem sitewide and have not determined the real problem yet, but the suggestion for Cygwin/Windows was to use RcsLite which has at least provided functionality for now. My error messages looked nearly identical. See topic OopsHangs.

-- JoshuaJohnston - 17 Feb 2006

It may be because you are trying to edit a topic that came from Cairo, and you haven't rcs unlocked it, as described in the TWikiInstallationGuide.

-- CrawfordCurrie - 17 Feb 2006

I had this problem in my new 4.1.2 installation. I found that I had forgotten to set the TEMP and HOME paramaters in my Windows server environment (as given in the cookbook). The problem got rectified after I set them and restarted apache

-- ChengappaCB - 22 Dec 2007