Bug: Create New Web Fails with useRcsDir

Create New Web gives "Error: Could not copy topics to the new web

The new web has been created, however not all topics could be copied from the base web.

Error message: Copy file ( /home/twiki/www/data/_default/WebChanges.txt,v, /home/twiki/www/data/Bayarea/WebChanges.txt,v ) failed, error: No such file or directory."

Test case

Create new installation with useRcsDir=1 and RCS dirs created according to installation guide. Figure out how to become an administrator (separate thread please smile ) and create a new web.

Environment

TWiki version: TWikiRelease01Feb2003
TWiki plugins: DefaultPlugin, EmptyPlugin, InterwikiPlugin
Server OS: Mandrake-Linux 9.0
Web server: remember my bug profile...
Perl version: 5.8.0
Client OS: same as server
Web Browser: galeon blecch

-- DavidKing - 27 Aug 2003

Follow up

Co-incidentally, I was trying to investigate why the latest revision always seems to be 1.1 no matter how many times a topic has been edited. It turns out that you need to add a line to TWiki.cfg:

 @storeSettings = ( # RcsLite and Rcs dataDir => $TWiki::dataDir, pubDir => $TWiki::pubDir, useRcsDir => $TWiki::useRcsDir, # added I Huneke 1 Sept 2003 attachAsciiPath => "\.(txt|html|xml|pl)\$", 

Maybe this would fix your problem too. An equivalent patch is described in DiffsRevertsToOneError.


Thanks, ImmoHuneke.

I see that you concur with JohnRouillard.

This proves there are at least two ways to solve DiffsRevertsToOneError. As a new twiki user, I had to step thru code to find the uninitialized value and put my fix there. You don't say whether this solution resolves CreateNewWebFailsWithUseRcsDir (this bug) but I'll try it when I get back to twiki.

Still, this class of error seems to be caused by redundancy in the config file. Maybe better to define important things once, like

 @storeSettings = ( useRcsDir => 1, ); 

or move @storeSettings out of the config file (doesn't guarantee happiness) or use structs or something to verify at compile time that $self has what it needs...

I guess another way to see if $self{xyz} is undefined is to continually scan the web server logs.

-- DavidKing - 01 Sep 2003

Fix record

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r3 - 2003-09-01 - DavidKing
 
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.