[Fwd: cvs commit: nothing known about `modulename']

[Alan M. Feldstein]

I've done some more work on this, but my question is the same: Do commit 
and tag support module names?

fonzie% cvs -d :ext:address@hidden:/var/lib/cvsroot commit sparc/model/fsm 
sparc/model/FullChip.java sparc/model/iu sparc/model/modules sparc/model/fpu
cvs commit: Examining sparc/model/fsm
cvs commit: Examining sparc/model/iu
cvs commit: Examining sparc/model/modules
cvs commit: Examining sparc/model/fpu
Enter passphrase for key '/home/alan/.ssh/id_rsa':
fonzie% cvs -d :ext:address@hidden:/var/lib/cvsroot commit Sputnik
cvs commit: cannot open CVS/Entries for reading: No such file or directory
cvs commit: nothing known about `Sputnik'
cvs [commit aborted]: correct above errors first!
fonzie%

Since the paths in the "Sputnik" alias module definition contain the 
name of the root directory of the sandbox (i.e. "sparc"), I have moved 
up to the parent directory of "sparc" this time for the commit attempts. 
This forces me to use the global -d option.

The first attempt above succeeded, where I substituted the alias module 
definition for the alias module name.

The second attempt above failed, where I used the alias module name. My 
theory is (treating CVS as a well-documented black box) that commit 
tried to find "Sputnik" as if it were a file or directory name. Failing 
this, and not wanting to report "nothing known", commit decided to look 
in CVS/Entries, still thinking that "Sputnik" is a file or directory 
name. When it couldn't find CVS/Entries (of course it won't find it from 
this directory), commit gave up and reported "nothing known".

Why doesn't commit look in the repository's administrative files (i.e. 
the modules file)? Something /is/ known about "Sputnik", and that is 
where it is known.

Does commit support module names? I have the same question about tag.

-------- Original Message --------
Subject:        cvs commit: nothing known about `modulename'
Date:   Thu, 20 Jul 2006 20:44:34 -0500
From:   Alan M. Feldstein <address@hidden>
Reply-To:       address@hidden
Organization:   Cosmic Horizon
To:     address@hidden



Using v1.11.6, can I not commit/tag by module name?

I proved that the module name was known to CVS by (unnecessarily) 
invoking checkout. I already had a sandbox that is a superset of the 
module. The checkout worked perfectly (as an update).

However, when I try to commit, this time from the root directory of the 
sandbox (but I have tried several obvious variations):

   cvs commit Sputnik
   cvs commit: nothing known about `Sputnik'

"Sputnik" is an alias module. The paths in the aliases are relative to 
the repository root directory, which is great for checkout, but 
inconvenient for commit if commit treats the module name as if the the 
paths had been specified instead. In other words, the paths contain the 
name of the root directory of the sandbox.

My theory is that the form of the paths is not relevant to the problem 
that commit knows about "Sputnik". It has to find the name before it can 
complain about what the name represents.

In v1.11.6, is commit capable of accepting a module name? I have the 
same question for tag.

--

Alan Feldstein

Cosmic Horizon logo

http://www.alanfeldstein.com/