Question

Having troubles to make RCSWrap work correctly (see RCSWrapCorruptsMyTopicsHistory), I'm trying RCSLite.

It works fine except that once a topic is saved, the lock in the txt,v file is emptied, preventing from switching to RCSWrap/RCSLite back and forth.

Before :

head   1.5;
access;
symbols;
locks
   nobody:1.5; strict;
comment   @# @;

After :

head   1.6;
access;
symbols;
locks; strict;
comment   @# @;

Is this normal ? Is there something I can do to prevent this ?

TIA.

Environment

-- JeromeBouvattier - 15 Sep 2005

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 notice a similar problem in exactly the same environment. In my case, the RCS lock is emptied only when I save with the "Release edit lock" turned on. (Added later: The problem cannot be reproduced to be closely connected with the edit lock. It turns up sometimes, and seems to be dependent on some additional factor I not yet fully understand, so I cannot reliably reproduce the situation although it remains very annoying to relock by hand every once in a while. ).

Now, supposing you have this turned on per default, then we have exactly the same problem.

-- ClemensCap - 07 Oct 2005

On my boxes, I can consistently reproduce the problem. Any topic modified with RCSLite, be the "Release edit lock" on or off, will see its RCS lock get emptied.

PS : Should I move this to Codev and turn it into a bug report ? How ?

-- JeromeBouvattier - 07 Oct 2005

I thinks there are two different storage systems involved. Your problems show up with Rcslite, mine with Rcswrap. Yours is reproducible, mine only on a randomized basis (having the server sit there doing nothing for a while increases the chances to see such an error).

Maybe let's wait another day or so if we get a response by some of the developers.

-- ClemensCap - 07 Oct 2005