info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: info-cvs Digest, Vol 54, Issue 19


From: Handape JUGARI
Subject: Re: info-cvs Digest, Vol 54, Issue 19
Date: Wed, 23 May 2007 07:45:32 +1000


Hey stop sending these information to me...


address@hidden writes:
Send info-cvs mailing list submissions to
address@hidden
To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.nongnu.org/mailman/listinfo/info-cvs
or, via email, send a message with subject or body 'help' to
address@hidden
You can reach the person managing the list at
address@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of info-cvs digest..."

Today's Topics:
   1. Re: Help: Protocol error: too many arguments (Dennis Jones)
   2. Re: cvs import ignore (Spiro Trikaliotis)
   3. RE: cvs import ignore (Koziel, Ryan)
   4. Re: RCS Error (Diego Ribeiro de Andrade)
   5. adding a non-empty directory to an existing project (Ji Li)
   6. Re: adding a non-empty directory to an existing project
(Mark E. Hamilton)

----------------------------------------------------------------------
Message: 1
Date: Tue, 22 May 2007 19:15:19 GMT
From: "Dennis Jones" <address@hidden>
Subject: Re: Help: Protocol error: too many arguments
To: address@hidden
Message-ID: <address@hidden>

"Arthur Barrett" <address@hidden> wrote in message news:address@hidden
I agree, it should not be happening at all.  I have the latest stable
release of CVS [version 1.11.22 as both client (Windows) and server
(FreeBSD)], and I have the latest TortoiseCVS (version
1.8.31).  When I

TortoiseCVS only works with CVSNT and includes it - if you want to keep
your server and client versions in sync as you suggest then you should
upgrade the server to CVSNT (yes it does run on linux).

I'm not going to convert the server to CVSNT -- it's too big of a risk, and converting doesn't buy me anything.

As I indicated before - sounds like a server issue, but without a trace
it is impossible to tell.

It could be, but since it has never happened before (never in 7 years) and since it seems to be a relatively unusual case, I'm not going to worry about it. - Dennis

------------------------------
Message: 2
Date: Tue, 22 May 2007 21:47:57 +0200
From: Spiro Trikaliotis <address@hidden>
Subject: Re: cvs import ignore
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii Hello,
* On Tue, May 22, 2007 at 11:38:50AM -0700 James. L wrote:
for some projects i do need to include a .so file -
for example a perl CPAN module may require compilation
and generate a .so file.

Use the "-I!" option.
HTH,
Spiro.
--
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/ http://www.viceteam.org/

------------------------------
Message: 3
Date: Tue, 22 May 2007 14:51:48 -0500
From: "Koziel, Ryan" <address@hidden>
Subject: RE: cvs import ignore
To: <address@hidden>
Message-ID:
        <address@hidden>
        
Content-Type: text/plain; charset="us-ascii" James,
You will have the same problem when you branch too regarding the empty
folders. I did the same thing you did, just create a dummy file and
leave it in the empty folder(s) so the folder is always created in the
branch. Haven't had a problem since, and it has been a couple of years.
We had a 'bin' folder that was empty and all projects compiled the
output to this 'bin' folder - which wasn't there after I imported or
branched. We could have tweaked the build to create the folder first,
but there were a lot of situations like this with the builds and a lot
of code that needed to be changed to accommodate. The dummy file seemed
the easiest and least-disruptive choice.
For the .so file. That is binary. You need to import this file in
differently than other, non-binary, files. I noticed this behavior too
when importing my projects initially. I just compiled a list of these
binaries and added them manually with the -kb arguments. I don't know if
CVS skips it on import due to it being binary or what...maybe it didn't
skip it and I am off. But either way, these need to be handled
differently. http://ximbiot.com/cvs/manual/cvs-1.11.7/cvs_9.html#SEC80
NOTE: The above link applies to the version of CVS that I am working
with. Backup to http://ximbiot.com and navigate to your version. -Ryan
-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of James. L
Sent: Tuesday, May 22, 2007 1:39 PM
To: Larry Jones
Cc: address@hidden
Subject: Re: cvs import ignore

--- Larry Jones <address@hidden> wrote:
James. L writes:
> > it turns out that those are empty directories.
once i
> create a dummy file, the directory import is fine.
> > why cvs behaving like this? Because CVS manages files, not directories.

i see. thanks.
> it also ignores .so file
> as mentioned in the cvs ignore list. what's the
reason
> behine this? .so is used for shared libraries on most Unix systems.

for some projects i do need to include a .so file - for example a perl
CPAN module may require compilation and generate a .so file.
i have no problem cvs doing this. but that means i have to keep
remembering checkin the .so files. the same goes for empty directories..
it feels like CVS gets in the way.
-Larry Jones

James.

________________________________________________________________________
____________
Don't pick lemons.
See all the new 2007 cars at Yahoo! Autos.
http://autos.yahoo.com/new_cars.html

------------------------------
Message: 4
Date: Tue, 22 May 2007 17:25:46 -0300 (BRT)
From: "Diego Ribeiro de Andrade" <address@hidden>
Subject: Re: RCS Error
To: "Garyl Erickson" <address@hidden>
Cc: address@hidden
Message-ID:
        <address@hidden>
Content-Type: text/plain;charset=iso-8859-1 Garyl,
 Thank you for the useful information you sent! Im tryng to follow your
tip to solve the problem. But Im having dificulties to cut the revisions
as the files are extense and has lot of revisions to analyse. But I wll
keep trying! :)
 This email a want to show you a interesting information... the result of
the execution of the script validate_repo.pl fount in the contrib folder.
We had a success of about 95,57% in this migration. So Im very confident
that we ll solve this question and start working on CVS as soon as
possible! Thanks for all. Any help, Tips or Ideas are very welcome! Regards. Diego.
 List of corrupted files
**** File:
33787sicapbsa/01-Sistema/05-ModeloVisual/units/ModeloProjeto/Realizacoes/SicapJava/DiferencasSalariais.cat
**** File:
33787sicapbsa/01-Sistema/05-ModeloVisual/units/ModeloRequisitos/SicapJava.cat
**** File:
33787sicapbsa/01-Sistema/05-ModeloVisual/Prototipo/Sicap/cdu_EPCnRstClc/IdentificacaoProcessoParte.html
**** File:
33787sicapbsa/01-Sistema/05-ModeloVisual/Prototipo/Sicap/cdu_EPCnRstClc/ListaParte.html
**** File:
33787sicapbsa/01-Sistema/05-ModeloVisual/Prototipo/Sicap/cdu_EPCnRstClc/ParametroCalculoConsolidado.html
**** File:
33787sicapbsa/01-Sistema/05-ModeloVisual/Prototipo/Sicap/cdu_EPCnRstClc/ModeloDemonstrativoConsolidado.rtf
**** File:
33787sicapbsa/01-Sistema/05-ModeloVisual/Prototipo/Sicap/cdu_EPCnRstClc/ListaProcesso.html
**** File:
33787sicapbsa/01-Sistema/05-ModeloVisual/Prototipo/Sicap/cdu_EPCnRstClc/TipoVisualizacao.html
**** File:
33787sicapbsa/01-Sistema/06-Implementacao/03-Controle/SicapParecer/SemTransacao.cls
**** File:
33787sicapbsa/01-Sistema/06-Implementacao/01-Aplicacao/SICAP/cdu_IGCnRIzCnAnPrc/ConsultaAnalitica.js
**** File:
33787sicapbsa/01-Sistema/06-Implementacao/01-Aplicacao/SICAP/cdu_CPCnCrgPrcTc/rngObterDados.asp
**** File:
33787sicapbsa/01-Sistema/06-Implementacao/02-Banco/SP/SICAP/dbo.spi_GravaLogErroAplicacao.PRC
**** File: 33787sicapbsa/01-Sistema/04-Projeto/01-Documentos/Modelo
Fisico/SICAP-MFD.PDM
**** File: 33787sicapbsa/01-Sistema/04-Projeto/01-Documentos/Modelo
Fisico/SICAP-DadosSiape-MFD.PDM
**** File:
33787sicapbsa/02-Projetos/CalculosEPericias/01-GestaoProjeto/01-Planos/SICAP-
CalculosEPericias-ED.xls
**** File:
33787sicapbsa/02-Projetos/CalculosEPericias/01-GestaoProjeto/01-Planos/SICAP-
CalculosEPericias-EDback.xls
List of Files That Don't belong in Repository:
**** File: 33787sicapbsa/baselines.csv
**** File: 33787sicapbsa/estado_baseline.csv
Total Files: 3757 Corrupted files: 16 Invalid revs: 0 Extra files: 2 Ignored Files: 0 Total Revisions: 0 Interesting Revisions: 0
Diego,
You can search for the \x3c (hex 3c?) in the rcs ,v file, which may give
you a clue as to what the problem is. The ,v file format is fairly
straightforward. Examine a few and you'll figure out the syntax. If you
want to go to the trouble to find out exactly where the problem is, you
can do a brute force approach. Manually cut revisions out of the ,v file
(make a backup first!) using a binary reduction method: cut out half the
revisions (and update the pointers to the last version, etc.); if it
still has a problem, cut out half of what's left. Repeat until you find
the section that caused the problem. I did this once when I had a
somewhat similar problem shown up by the log command, see the cvsnt
emails attached below.
Good luck,
Garyl

address@hidden wrote:
Hi all,
 Im on a effort to migrate a lot of projects from Clear Case to CVS.
Some
of these projects were migrated well with no problems. Some of them
needed to be repaired manually and after that worked well.
 Most of these projects have a average number of files about 700 with an
average number of revisions for each file about 30.
 Im now in charge with a Bigger project of 3700 files and about 60
revisions for each file. Most of the RCS files generated are working
well. But some of them are not, and CVS give up when Im tryng to analyse
with "log" command or retireve a older revision. A example of what is going on is this message:
 -f [log aborted]: unrecognized operation '\x3c' in
/opt/cvs/rep/somefile.html,v
 This code '\x3c' varies for each "corrupted/misfunctioning" file.  This
occurs for some files, and I dont know what could be happening. Does
someone had experienced a problem like that before? Best Regards! Thanks for ALL!
Diego.

------------------------------------------------------------------------
Subject:        [cvsnt] mismatch in rcs file between deltas and deltatexts
Date:   Fri, 06 Apr 2007 09:25:08 -0700
From:   Garyl Erickson <address@hidden>
Organization:   Veicon Technology, Inc.
To: address@hidden


I have one file in my repository that I can't run cvs log on. It fails
on most cvs log commands, except for -t and -h (with or without -N),
with the following message: [log aborted]: mismatch in rcs file
source-file-pathname,v between deltas and deltatexts").
I have no problems with any other CVS commands I've tried on that file.
I can check out every available revision of it, do diffs between
revisions, etc., so the deltas in the RCS file seem to be (mostly?) ok,
despite the error message. I've also looked at the ,v file in some
detail and compared it to others. I don't claim to be an expert but it
seems to match the pattern of the others. One thing that's different
than most is this file was renamed and moved to a different directory at
some point and the initial revision is 1.26. But starting a file with a
specific revision number should work, and I have others that do that
work fine. The earliest revision found in the ,v has a blank next field.
Using -ttttttt indicated the last sub logged was RCS_fully_parse(),
which, after a very cursory look, seems to output the mismatch error if
it can't find a particular version it's looking for (is that right?) Are there any tools to analyze the ,v file in more detail or to repair it? Any other ideas how to debug or fix this?
Thanks,
Garyl

P.S. I'm running CVSNT 2.5.03 (Scorpio) Build 2151 on Windows Server 2000.
_______________________________________________
cvsnt mailing list
address@hidden
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt ------------------------------------------------------------------------
Subject:        Re: [cvsnt] mismatch in rcs file between deltas and deltatexts
-- fixed
Date:   Wed, 18 Apr 2007 13:05:19 -0700
From:   Garyl Erickson <address@hidden>
Organization:   Veicon Technology, Inc.
To:     address@hidden
References:
<address@hidden>

This was still bugging me so I finally resorted to brute force to figure
out what was wrong with the ,v file. I manually cut revisions out of the
,v file (using a binary reduction method: cut out half the revisions; if
it still has a problem, cut out half of what's left, etc.) until I found
the section that caused the problem. It was a log and text (diff)
section for rev 1.84.2.1. This branch was not mentioned in the symbols
section at the top of the file, i.e., there was no tag for the branch
1.84.0.2.
After looking at other files in the repository, I added a symbol for the
branch at the right place:  v2-patches:1.84.0.2, but I still couldn't
log the file. Since the change in the rev 1.84.2.1 file on the branch
was also on the trunk, and there was no mention of this branch in a
branch field in this file (meaning no revisions on this branch were
otherwise known), and there didn't appear to be any revisions on that
branch tagged in other files, and it's old (past support), and there was
no mention of anything related in other documentation, I just deleted
the anomalous log and text section. This cleared up the logging problem.
Whew!
Of course, the question still remains as to how this happened. It's as
if someone attempted to remove a branch (perhaps manually?), but didn't
completely succeed. More comments below... Garyl

Arthur Barrett wrote:
Garyl
One thing that's different than most is this
file was renamed and moved to a different directory
at some point
Was that with "cvs rename" ?
Probably not, as I don't think we were aware of the cvs rename command.
Does it support a directory change? It was most likely done using the
"normal" procedure using copy /old-filename //new-filename, /cvs add
/new-filename/, cvs remove /old-filename/, and cvs ci -r/rev/. Both the
old (dead) and new files exist and I can run cvs log on the old
filename. The comment for its last revision says it was renamed to the
new filename. According to the ,v file for the new file, its first
revision is the same as the last revision of the old filename. Both the
last revision of the old file and the first revision of the new file
have the same comment and the same commitid.
and the initial revision is 1.26. But starting a
file with a specific revision number should work
Yes it *should* but it is not recommended and probably not tested for
years.
FYI, it seems to work fine for other files in this repository, and now
this one, once the vestiges of the deleted branch were removed.
Are there any tools to analyze the ,v file in
more detail or to repair it?
You've done it already - "cvs log" is the way to analyze the ,v file...
P.S. I'm running CVSNT 2.5.03 (Scorpio) Build 2151
on Windows Server 2000.
If possible please upgrade to 2.5.03.2382 - but it probably wont fix
this...
If it still occurs - send the RCS file to address@hidden and we
will file it and put it on the bug list.  We won't look at it for a
while - but we'll never look at it unless we have a test set... Regards,

Arthur
_______________________________________________
cvsnt mailing list
address@hidden
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

--
Diego Ribeiro de Andrade.
Analista de Suporte.
Smart Tech Consulting.
+55 21 2532 6335
+55 21 9400 5854
msn: address@hidden
"Por certo, os que não obtêm dentro de si os recursos necessários para
viver na felicidade acharão execráveis todas as idades da vida".
Marcus Tullius Cicero

------------------------------
Message: 5
Date: Tue, 22 May 2007 17:37:53 -0400
From: "Ji Li" <address@hidden>
Subject: adding a non-empty directory to an existing project
To: <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset="us-ascii" Hi,
I have an existing project in CVS repository. Now I want to add a directory
containing several files to this project as a subdir. I tried adding the
subdir first, then adding all files in the directory. After that, the CVS
repository looks correct. But when I tried to load the new subdir at another
machine (under the same project) using "cvs update", the new subdir won't
show up. How should I do it?
I guess some one should have asked similar questions before, but I couldn't
find in the archive. Thanks! -Ji
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/pipermail/info-cvs/attachments/20070522/add4e970/attachment.html ------------------------------
Message: 6
Date: Tue, 22 May 2007 15:41:04 -0600
From: "Mark E. Hamilton" <address@hidden>
Subject: Re: adding a non-empty directory to an existing project
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=windows-1252; format=flowed
Ji Li wrote:
that, the CVS repository looks correct. But when I tried to load the new subdir at another machine (under the same project) using “cvs update”, the new subdir won’t show up. How should I do it?

cvs update -d
--
----------------
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
505-844-7666 ------------------------------
_______________________________________________
info-cvs mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/info-cvs

End of info-cvs Digest, Vol 54, Issue 19
****************************************




reply via email to

[Prev in Thread] Current Thread [Next in Thread]