cvs-dev
[Top][All Lists]
Advanced

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

[Cvs-dev] Re: [Cvs-cvs] ccvs ChangeLog NEWS src/ChangeLog src/import.c .


From: Mark D. Baushke
Subject: [Cvs-dev] Re: [Cvs-cvs] ccvs ChangeLog NEWS src/ChangeLog src/import.c ...
Date: Sat, 16 Jun 2007 00:56:13 -0700

Hi Derek,

I have problems on GNU/Linux running with your latest patches.
To reproduce, try the following:

  sh sanity.sh -r `pwd`/cvs import-CVS

There will be an error message in check.log looking like this:

cvs [import aborted]: reading CVS/Tag: Not a directory
exit status was 1
FAIL: import-CVS-2

which is generated by the send_repository function in client.c 
file on line 3382:

        error (1, errno, "reading %s", adm_name);

where adm_name is CVS/Tag ...

The root cause seems to be that client_import_setup () believes that it
can accept what it sees in the /tmp/cvs-sanity/cvsroot/import-CVS
directory value of the repository it is sending as being viable for this
host.

I suspect that CVS needs to be able to tell send_repository to ignore
CVS_ADM directory entries... somehow. I have not paid close enough
attention to the nature of your most recent checks to grok in fullness
what needs to occur. Possibly there needs to be a flag added for
send_repository () to treat the directory as something which may contain
invalid 'CVS' entities and ignore them?


In other news...

I have a tree wherein I have an update to use the latest GNULIB files
(patch attached). There are a few problems with it regarding the
windows-NT port...

For the windows bulid of CVS, there are problems with the GNULIB use
of this idiom:

#if @HAVE_INCLUDE_NEXT
# include <foo.h>
#else
# include @ABSOLUTE_FOO_H@
#endif

for the following files:

    dirent_.h
    fcntl_.h
    float_.h
    stdio_.h
    stdlib_.h
    string_.h
    sys_stat_.h
    time_.h

I am not certain I understand how to generate the appropriate versions
of the windows-NT/*.h files. I don't believe that I understand the
pathname for the various ABSOLUTE_FOO_H values to be used... assuming
that there is a windows standard install path for them.

Any suggestions? In the worst case, I figure I could just commit the
patch and let someone else that has a window-NT box help sort things out
later to come up with a suitable replacment for each of the .h files as
needed.

        Thanks,
        -- Mark

Attachment: cvs.gnulib.patch
Description: CVS update for GNULIB as of 2007-06-12.


reply via email to

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