Réf. : Re: Réf. : Re: Re : [cvsnt] Unknown expansion option ' æ'
feymard at stago.fr
feymard at stago.fr
Wed Jun 1 10:37:07 BST 2005
Tony Hoyle
<tmh at nodomain.org Pour : cvsnt at cvsnt.org
> cc : (ccc : Franck-Sébastien EYMARD/GENNEVILLIERS/STAGO)
Envoyé par : Objet : Re: Réf. : Re: Re : [cvsnt] Unknown expansion option ' æ'
cvsnt-bounces at cvs
nt.org
31/05/2005 14:56
feymard at stago.fr wrote:
> > I use Windows (both client and server) and have this problem too (not
on
> > one file: hundreds can be corrupted)
>
> Can you repeat it?
>
> Is it the same as the OP or is it just random corruption (which would
> indicate failing hard disk/bad drivers).
>
> Tony
I had to bring old archives in a repository. Between 2 versions, I can have
a lot of deleted files. In this case, I make a cvs remove on the module,
cvs commit, push the new version and readding these files. But, when I
commit this updated sandbox, on some files (modified ones, binaries or
ascii), the kopt in CVS/Entries become strange.
But, when I force files in binary (for ascii ones; both ascii and binaries
files could be corrupted), the next commit make this:
Dans C:\travailCVS\tentative bug : "C:\Program Files\TortoiseCVS\cvs.exe"
"commit" "-m" "" "TP/STB100/NULL" "TP/STB100/OFFSET" [... many other
files...] "TP/TURBO.TPL"
CVSROOT=:pserver:feymard at cvsnt-be:/Repotest01
cvs.exe commit: Unknown expansion option 'Í'.
cvs server: Unknown expansion option 'Í'.
cvs server: Unknown expansion option 'Í'.
cvs server: Unknown expansion option 'Ñ'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'Ó'.
cvs server: Unknown expansion option 'É'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Ë'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Í'.
cvs server: Unknown expansion option 'Í'.
cvs server: Unknown expansion option 'Í'.
cvs server: Unknown expansion option 'Ì'.
cvs server: Unknown expansion option 'Ì'.
cvs server: Unknown expansion option 'Ì'.
cvs server: Unknown expansion option 'Ì'.
cvs server: Unknown expansion option 'Ì'.
cvs server: Unknown expansion option 'Ì'.
cvs server: Unknown expansion option 'Ì'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Ë'.
cvs server: Unknown expansion option '>'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Ì'.
cvs server: Unknown expansion option 'Ë'.
cvs server: Unknown expansion option 'Ì'.
cvs server: Unknown expansion option 'Î'.
cvs server: Unknown expansion option 'Î'.
Checking in TP/STB100/NULL;
Succès : opération CVS terminée
The corruption is now corrected: the commit ends successfully and theses
errors will not reappear (only on binaries: ascii files keep the corruption
visible).
When the commit fails, I edit 'entries' file to put a corrected option (-kb
for all corruptions: -kv or -kkv are overwritten by the commit with the bad
extension)
I test on 2 different servers (win2k on a desktop PC, and a 2003 on the
real server): this can't be a hardware/driver problem.
In "C:\travailCVS\tentative bug\TP\STB100\CVS\entries" there is an example
of corruption:
[...]
/TTASK.PAS/1.1/Thu Apr 5 12:58:36 2001/-kkv/
/NULL/0/dummy timestamp/-kÍ/
/PRNFILE.PAS/0/dummy timestamp//
[...]
Go on server to see NULL,v
head 1.2;
access;
symbols
v106-05:1.1;
locks; strict;
comment @# @;
expand @b@;
1.2
date 2005.05.31.16.35.19; author feymard; state dead;
branches;
next 1.1;
deltatype text;
permissions 444;
commitid d48429c9206052c;
kopt Í;
filename NULL;
1.1
date 2005.05.31.15.46.14; author feymard; state Exp;
branches;
next ;
deltatype text;
permissions 666;
commitid a24429c86a7600a;
kopt b;
filename NULL;
[...]
An other example: after the commit (why the corrumption become not visible)
(file: CVOLCONE.EXE,v )
1.3
date 2005.05.31.16.50.59; author feymard; state Exp;
branches;
next 1.2;
deltatype text;
permissions 666;
commitid 288429c95b91141;
kopt b;
filename CVOLCONE.EXE;
1.2
date 2005.05.31.16.35.10; author feymard; state dead;
branches;
next 1.1;
deltatype text;
permissions 444;
commitid d48429c9206052c;
kopt Ñ;
filename CVOLCONE.EXE;
1.1
date 2005.05.31.15.46.11; author feymard; state Exp;
branches;
next ;
deltatype text;
permissions 666;
commitid a24429c86a7600a;
kopt b;
filename CVOLCONE.EXE;
[...]
1.2 is the cvs remove of the whole module.
Is there a bad use of my repository, or is it a hidden feature on reborn
files? ;)
(here, this test was made on our real server, a 2.5.01 build 1969 on a 2003
server, french edition)
More information about the cvsnt
mailing list