Re: Mystery for a cvsgui expert

Thanks, Oliver. Answers in-line below:

--- In [email protected], Oliver Giesen <ogware@...> wrote:
>
> Sorry, no definite ideas so far, just a couple of things to note, 
> without guarantee that this has anything at all to do with the issue at 
> hand:
> 
>     * Your CVSROOT string looks incomplete. The :local:-protocol should
>       require a fully-qualified path, including the drive name if you're
>       on Windows. From what you've written, I would expect that it
>       should be :local:c:\Users\Administrator\Repos\CVS
[Paul] - I see your point, but bear in mind that the path without the drive letter had been working for several other recursive add attempts including the many files that were successfully added in the same attempt where several were not. After adding the drive letter, the result was still the same for the individual file because of course the strange path it gives is still wrong.
>     * The warning about "ssh" not being a recognized command looks like
>       for some reason it was attempted to use the :ext: protocol which
>       in the pre-CVSNT days was how you connected to a CVS server via
>       SSH. "ssh" is simply the implied default name of the external
>       tunnelling client to use in that case and if you don't have such
>       an executable on your PATH you would get that message. If you do
>       want to use an external tunnelling client you can override the
>       default by setting the CVS_RSH environment variable.
>     * Using the -d commandline argument with the add command makes no
>       sense: You only need that argument when you are running commands
>       outside a sandbox, yet the add command can only be run when you
>       are inside a sandbox directory (i.e. the directory needs to be
>       added first before you can add the file inside it - see our
>       previous discussion).
[Paul] - WinCVS must add this because the Admin > Command Line utility runs in a context outside (or at least independent of) the known sandbox. I did not enter that argument in the Command Line utility. I selected the "Execute for directory" option, entering the correct directory path, and WinCVS adds that to the given command.
>     * Why were you trying to add files using Admin|Command Line? There
>       are toolbar buttons for the Add command. Also, did you know that
>       you can simply enter cvs commands into the console pane?
[Paul] - From what I read, CVS does not support a global CVSROOT any more, so the toolbar buttons have no way of knowing which cvs root to use. That is obviously why the CVSROOT is asked for in the Admin > Command Line utility. Of course I tried the toolbar buttons first, and did not, and do not, work. At this point, the toolbar button error message is the same as with the Command Line utility.
>     * As with the regular Add command you can only run the Recursive Add
>       macro in a directory that has already been added. The error
>       messages you're quoting do not quite fit that suspicion, though.
>       Could it be that at some point during your trying out different
>       things you set the CVSROOT environment variable? If so, what does
>       it say? My guess is that it contains something that either
>       explicitly specifies the :ext:-protocol or that it is missing a
>       protocol prefix altogether so that CVS is forced to guess the
>       protocol by heuristics and is for some reason incorrectly guessing
>       at :ext:.
[Paul] - Yes, the parent directory has already been successfully added to the repository. I have not set any CVSROOT environment variable in my system. I have only set it for the Command Line utility, once for the first use, and thereafter WinCVS remembers it. In the Command Line utility I am explicitly setting the CVSROOT to ":local:C:/Users/Administrator/Repos/CVS" (without the quotes). And again, it has worked without the "C" drive specification previously.
>     * Not setting up an unknown file extension before running the
>       Recurisve Add macro can have no effect here. The macro would
>       simply default to "Default" and you can obviously still change
>       that before hitting OK.
>     * Even if you did add a file with the wrong file type it is
>       technically impossible for that to have any effect on what happens
>       when trying to add any other files. That's one of the few
>       advantages of CVS' file-based repository...
> 
> Before you run the Recursive Add macro, what CVSROOT and repository path 
> are displayed in the status bar?
[Paul] - Something very strange indeed, although not unfamiliar. It shows:
":ext:[email protected]:/cvsroot"   "pw/frame/base/actions"

That ext and CVS server information belongs to a project that I was once a part of a long time ago, using a completely different computer. Now, I know that there are things that I have copied from other computers I've had onto this one, but if you could tell me where it might be getting that from, it may help me pinpoint how and where I got WinCVS mixed up. I do not want or need that CVS access information, I need the local information that we've been discussing here. -- Good question!
> 
> Could you maybe post the complete output from the Recursive Add macro up 
> to the first occurrence of the spurious "ssh" error message?
[Paul] - SUre. To keep it simple I applied the Recursive Add to a directory with no sub-directories and only one file to be added. The resulting output was (in total):


analyzing selection...
analyzing selection...
	C:\EC Dev\Module\framework\base\actions
reorganizing file list...
adding files and folders...
[ERROR] cvs add: warning: unrecognized response `'ssh' is not recognized as an internal or external command,' from cvs server
cvs add: warning: unrecognized response `operable program or batch file.' from cvs server
cvs [add aborted]: end of file from server (consult above messages if any)

Added 0 folders and 0 files

> 
> Cheers,
> 
> Oliver
> 
> Am 06.09.2009 22:48, schrieb psumares:
> > My WinCVS app just got messed up for some strange reason; perhaps someone out there can help me solve this mystery and then fix the issue, based on the following clues.
> >
> > - It happened right after I used the "Recursive Add" macro. Some of the files were added but then a bunch of errors started streaming out, and many of the files were not added.
> >
> > - The error messages were primarily this one, which others have experienced when using a ":pserver" host type (NOTE that I am only using a local CVS ROOT):
> >
> > "[ERROR] cvs add: warning: unrecognized response `'ssh' is not recognized as an internal or external command,' from cvs server
> > cvs add: warning: unrecognized response `operable program or batch file.' from cvs server
> > cvs [add aborted]: end of file from server (consult above messages if any)"
> >
> > - I realized that I had not yet configured one of the file types I was trying add, using the "Recursive Add Options" utility. However, setting this type among the appropriate "Default Unicode Extensions" did not resolve the issue upon a reattempt.
> >
> > - During the recursive add attempt I selected to ignore certain file extensions, like ".log".
> >
> > - During the recursive add attempt I also selected to "autocommit", adding a commit message.
> >
> > - A subsequent commit of the files that *were* added succeeded.
> >
> > - Unfortunately, all attempts to add recursively to the repository now fail with the "ssh" error pasted above.
> >
> > - An attempt to add a single file with the Admin>  Command Line utility failed with the following (very strange) error message:
> >
> > "cvs -d :local:/Users/Administrator/Repos/CVS add CA_ECBrain_Thought_Edit.cls (in directory C:\EC Dev\Module\framework\base\actions)
> > cvs [add aborted]: Directory /Users/Administrator/Repos/CVS/pw/frame/base/actions does not exist on the server"
> >
> > What is strange here is that there I never specified any such path that had "pw/frame/base/actions" in it. It should be as described in the first part of the output, "framework/base/actions". Where did it get this "pw/frame/base" thing from?
> >
> > - The only coincidence about the point above is that *one* of the many files that did *not* get added correctly was called "PW_Frame.cls". And ".cls" was one of the extension types that I had failed to tell WinCVS was a "Default Unicode Extension" type. I'm not sure if that's related at all, but note the similar pattern between this file name and that strange path that seems to have come out of no where, and is not recognized.
> >
> >
> > Does anyone have any ideas about what may be going on here, based on the above clues? WinCVS seemed to be in a bad state now, and if I can't add files, I will have to abandon any how of using this system.
> >
> > Thanks in advance.
> >
> > Paul Sumares
> >    
> 
> 
> 
> [Non-text portions of this message have been removed]
>




------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/cvsgui/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/cvsgui/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/