Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Hi, I'm wondering if anyone's seen this behaviour before. I regularly import module snapshots using the following 'import' command (this is with client/server 2.0.58d on Win2K): cvs -q import -m "<text>" -ko -I! <module_path> <vendor_tag> <release_tag> A recent import succeeded, but subsequent checkout illustrated a repository corruption during the original import. In particular I see the following messages during the checkout: cvs server: Unknown expansion option 'ô'. cvs server: invalid RCS expansion flags Indeed, when I look at the repository file directly I see the following corruption (see kopt): 126.96.36.199 date 2007.01.23.16.30.44; author davidh; state Exp; branches; next ; deltatype text; permissions 644; commitid af045b638303e80; kopt ; filename @something.c@; The cvs log result for this file indicates the following for the imported vendor branch revision: ---------------------------- Revision : 188.8.131.52 Date : 2007/1/23 16:30:44 Author : 'davidh' State : 'Exp' Lines : +11 -2 Description : ; commitid: af045b638303e80; filename: something.c; Import of such and such snapshot. The expansion flag (as seen in the kopt field) is clearly corrupted. Anybody know how this might happen and how I can prevent it from happening? I haven't tried eliminating the -ko from the import, but I imagine this would have an effect; however, I'd rather not have to do that as the -ko is meaningful for most of my imports (i.e., for new files that get added during the import). Incidentally, none of my previous imports shows the 'commitid' field. Not exactly sure why that is (previously imports used the same command-line and same version of client/server) or whether it's relevant here or not... Thanks in advance for any help, -David