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 sales@march-hare.com.
Hello all,
Does anybody know why I get the "nothing known" errors? They don't seem to
be consistent.
In the first global update, it says "nothing known about Firmware". But
"Firmware" is a result of adding it in that sandbox and definitely is and
has been known through many updates and additions. Firmware.Sender, OTOH,
is a result of a checkout of the tag tTAG of the 1/2/Firmware module, using
a name override for the checkout directory. When updating Firmware by
itself, it is all of a sudden known. But when updating Firmware.Sender by
itself, it is first unknown, but then updated nonetheless.
Then I repeated the first update command, but with a file argument of ".".
AIUI, this should have the same effect, but it doesn't. When it gets to
updating the directory Firmware.Sender, it starts updating from the root of
my repository. See command 33 below.
The directory structure in the repo is like this:
1/
2/
Documents
Electronics
Firmware
Manuals
Mechanics
Parts
The dir structure in the sandbox is like this:
1\
2\
Documents
Electronics
Firmware
Firmware.Sender
Manuals
Mechanics
Parts
Can anybody make any sense out of this? Why the "unknown" messages? Why two
different ones? Why does it update Firmware.Sender after it says it's
"unknown"? Why don't I get an "unknown" message with "update ."? Why does
it start an update from the repo root when running "update ." and not when
running "update"? Where would those files (from the "up .") have gone in
the sandbox if I hadn't used the -n global option? (The 1\2\Firmware.Sender
directory contains 1/2/Firmware. So where would have gone the 1/3 module,
or the 4 top level module?)
When creating such additional checkouts (like the Firmware.Sender), I've
seen different behavior. I'm not sure what causes this. What I'd like to
see is that the Firmware.Sender directory is listed in 1\2\CVS\Entries. I
think I've seen it happen that such a checkout ends up there, but in this
case it didn't. What would cause it being there or not being there? If it
were there, would this "fix" the "update ." behavior?
Thanks,
Gerhard
<P:\1\2>21>cvs -n up
cvs server: Updating .
cvs server: Updating Documents
cvs server: Updating Electronics
...
cvs server: Updating Firmware
cvs server: Updating Firmware/Board
...
cvs server: Updating Manuals
cvs server: Updating Mechanics
cvs server: Updating Parts
cvs server: nothing known about Firmware
cvs server: Updating Firmware.Sender
cvs server: Updating Firmware.Sender/Board
...
<P:\1\2>25>cvs -n up -l Firmware
cvs server: Updating Firmware
<P:\1\2>26>cvs -n up -l Firmware.Sender
cvs server: nothing known about Firmware.Sender
cvs server: Updating Firmware.Sender
<P:\1\2>27>cvs -ttt -n up -l Firmware.Sender
10:32:59: -> Tracelevel set to 3. PID is 5436
10:32:59: -> Session ID is 153c469f680b3c0c
10:32:59: -> Session time is Thu Jul 19 13:32:59 2007
10:32:59: -> CVS Server is acting as standalone
10:32:59: -> main loop with CVSROOT=:sspi:user at server:/projects
10:33:00: -> Server codepage is CP1252
10:33:00: -> Client codepage is CP1252
10:33:00: -> Server version is CVSNT 2.5.03 (Scorpio) Build 2151
10:33:00: -> Client version is CVSNT 2.5.03 (Scorpio) Build 2151
10:33:00: -> Requesting server cvsignore
10:33:00: -> wrap_add(*.a -kb, 0, 0, 0, 0)
...
10:33:00: -> wrap_add(*.Z -kb, 0, 0, 0, 0)
10:33:00: -> Requesting server cvswrappers
10:33:00: -> wrap_add(*.h -k 't', 0, 1, 0, 0)
...
10:33:00: -> wrap_add(*.jar -k 'b', 0, 1, 0, 0)
10:33:00: -> Requesting server cvsrc (read-cvsrc2)
10:33:00: -> Parsing global cvsrc started
10:33:00: -> cvs -rx
10:33:00: -> checkout -P
10:33:00: -> update -P
10:33:00: -> Parsing global cvsrc finished
10:33:00: -> Name_Repository((null),)
10:33:00: -> Repository = /projects/1/2
10:33:00: -> Mapped repository = /projects/1/2
10:33:00: -> Name_Repository(Firmware.Sender,Firmware.Sender)
10:33:00: -> Name_Repository((null),Firmware.Sender)
10:33:00: -> Repository = /projects/1/2/Firmware
10:33:00: -> Mapped repository = /projects/1/2/Firmware
cvs server: nothing known about Firmware.Sender
10:33:00: -> main loop with CVSROOT=:sspi:server:/projects
10:33:01: -> Server codepage is CP1252
10:33:01: -> Client codepage is CP1252
10:33:01: -> Server version is CVSNT 2.5.03 (Scorpio) Build 2151
10:33:01: -> Client version is CVSNT 2.5.03 (Scorpio) Build 2151
10:33:01: -> Requesting server cvsignore
10:33:01: -> wrap_add(*.a -kb, 0, 0, 0, 0)
...
10:33:01: -> wrap_add(*.Z -kb, 0, 0, 0, 0)
10:33:01: -> Requesting server cvswrappers
10:33:01: -> wrap_add(*.h -k 't', 0, 1, 0, 0)
...
10:33:01: -> wrap_add(*.jar -k 'b', 0, 1, 0, 0)
10:33:01: -> Requesting server cvsrc (read-cvsrc2)
10:33:01: -> Parsing global cvsrc started
10:33:01: -> cvs -rx
10:33:01: -> checkout -P
10:33:01: -> update -P
10:33:01: -> Parsing global cvsrc finished
10:33:01: -> Name_Repository((null),)
10:33:01: -> Repository = /projects/1/2
10:33:01: -> Mapped repository = /projects/1/2
10:33:01: -> Name_Repository(Firmware.Sender,Firmware.Sender)
10:33:01: -> open_directory(/projects/1/2/Firmware,tTAG,(null))
10:33:01: -> Name_Repository(Firmware.Sender,Firmware.Sender)
10:33:01: -> Name_Repository((null),Firmware.Sender)
10:33:01: -> Repository = /projects/1/2/Firmware
10:33:01: -> Mapped repository = /projects/1/2/Firmware
10:33:01: -> wnt_stat(.cvsignore)
10:33:01: -> _statcore(00000000,.cvsignore)
10:33:01: -> Trying GetFileAttributesEx....
10:33:01: -> File attributes = 00002021
10:33:01: -> - FILE_ATTRIBUTE_READONLY
10:33:01: -> GetUnixFileModeNtEA(.,000000BC) returns 0666
...
10:33:01: -> wnt_stat(XBee-Sender.pro)
10:33:01: -> _statcore(00000000,XBee-Sender.pro)
10:33:01: -> Trying GetFileAttributesEx....
10:33:01: -> File attributes = 00002021
10:33:01: -> - FILE_ATTRIBUTE_READONLY
10:33:01: -> GetUnixFileModeNtEA(X,000000BC) returns 0666
10:33:01: -> close_directory()
cvs server: Updating Firmware.Sender
<P:\ASaP\RFPaddles>33>cvs -n up .
cvs server: Updating .
cvs server: Updating Documents
cvs server: Updating Electronics
...
cvs server: Updating Firmware
cvs server: Updating Firmware/Board
...
cvs server: Updating Manuals
cvs server: Updating Mechanics
cvs server: Updating Parts
cvs server: Updating .
cvs server: Updating 1
...
[follows full update from the repository root]
<P:\1\2>39>!type CVS\Entries
D/Documents////
D/Electronics////
D/Parts////
D/Firmware////
D/Mechanics////
D/Manuals////
/.cvsignore/1.1/Wed May 31 18:35:51 2006//
/0index.txt/1.4/Tue Jul 10 23:25:32 2007//
<P:\1\2>40>!type Firmware.Sender\CVS\Repository
1/2/Firmware
<P:\1\2>41>!type Firmware.Sender\CVS\Entries
/.cvsignore/1.5/Mon Mar 12 00:27:31 2007//TtTAG
/0index.txt/1.3/Fri Mar 23 18:32:18 2007//TtTAG
...
<P:\1\2>42>!type Firmware\CVS\Repository
1/2/Firmware
<P:\1\2>43>!type Firmware\CVS\Entries
/.cvsignore/1.7/Mon Jul 9 21:17:20 2007//
/0index.txt/1.5/Mon Jul 9 21:09:32 2007//
...