git-cvsserver won't add new content on update

git-cvsserver won't add new content on update

[Andy Parkins]

Hello,

I am trying to use git-cvsserver to supply CVS access to my git repository.  
The checkout worked okay, but now, during normal operation, I've made changes 
and added content.  After a cvs update the changed files all seem to have 
been updated as expected, however the added files are not being added.  
However, CVS is reporting that the file is added; but it never appears.

some/sub/directory$ cvs update
A some/sub/directory/file.c

After the above the file is not created.  Repeated cvs update calls result in 
the same output everytime.  I've tried it from the root of the tree (in case 
it was a path issue) and that fails in the same way.  I've tried specifying 
the path explicitly and that doesn't help either.  cvs status reports that 
the file is "Status: Needs Checkout".

A new cvs checkout in a different directory does get the new file, so this is 
a problem with updates only.

I'm not familiar with CVS so it could easily be that I've not understood; 
however the CVS tutorials say that this should be giving "U" output instead 
of "A" output.

So: is this a bug, or is it that (as usual) I've not done something terribly 
simple.


Andy
-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com

Re: git-cvsserver won't add new content on update

[Shawn O. Pearce]

Andy Parkins <andyparkins@gmail.com> wrote:
> I am trying to use git-cvsserver to supply CVS access to my git repository.  
> The checkout worked okay, but now, during normal operation, I've made changes 
> and added content.  After a cvs update the changed files all seem to have 
> been updated as expected, however the added files are not being added.  
> However, CVS is reporting that the file is added; but it never appears.
> 
> some/sub/directory$ cvs update
> A some/sub/directory/file.c

You need to commit first to get the file completely added.
What you are seeing above is that the file was listed in
some/sub/directory/CVS/Entries so that the next commit will
know to upload the file to the server.  Until then its not
actually going to do that...

-- 
Shawn.

Re: git-cvsserver won't add new content on update

[Martin Langhoff]

On 1/19/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> You need to commit first to get the file completely added.
> What you are seeing above is that the file was listed in
> some/sub/directory/CVS/Entries so that the next commit will
> know to upload the file to the server.  Until then its not
> actually going to do that...

yup. Also make sure you are using a really recent git-cvsserver, I
recently fixed a couple of problems related to file adds.

cheers.


martin

Re: git-cvsserver won't add new content on update

[Andy Parkins]

On Thursday 2007, January 18 16:22, Shawn O. Pearce wrote:

> You need to commit first to get the file completely added.
> What you are seeing above is that the file was listed in
> some/sub/directory/CVS/Entries so that the next commit will
> know to upload the file to the server.  Until then its not
> actually going to do that...

I've mislead you.  The file was added in the git repository.  It got there 
fine; it's therefore not in the Entries file.  I'm merely trying to get the 
file to appear in the CVS sandbox.



Andy

-- 
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com

Re: git-cvsserver won't add new content on update

[Andy Parkins]

On Thursday 2007, January 18 19:01, Martin Langhoff wrote:

> yup. Also make sure you are using a really recent git-cvsserver, I
> recently fixed a couple of problems related to file adds.

I've just tried again with the git-cvsserver from current next, with the same 
result.

I also repeated with pu and got the same result.  In all cases, the log is 
showing the "Tell the client the file will be added" message; which seems 
correct.


Andy

-- 
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@gmail.com