What do you see in the CVS/Entries file for the corresponding directory
that is showing those 'greek' filenames?
Yep, you're right. That's where the greek filename is coming from.
That would be a matter of looking in bug tracking for your vendor
(Redhat for version 7.1) to see if there were
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Jones [EMAIL PROTECTED] writes:
What do you see in the CVS/Entries file for the corresponding directory
that is showing those 'greek' filenames?
Yep, you're right. That's where the greek filename is coming from.
Okay. Now to try to figure
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark D.
Baushke
Sent: Wednesday, January 14, 2004 4:48 AM
To: Andy Jones
Cc: [EMAIL PROTECTED]
Subject: Re: Have I got a corrupt repository?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Jones [EMAIL PROTECTED] writes:
What do you see
If you are at version 2.4.20-28.7 of the kernel and glibc-2.2.4-33, then
I doubt that there is an mmap bug around any longer. If you are not at
that level, you may wish to look into getting some updates from
ftp://updates.redhat.com/7.1/en/os/ while they are still available.
We've not made any
As a suggestion to tackling this problem from a different direction,
would you please
run the check_cvs script over your repository. The script should be
found in the scripts
directory of the cvs distribution. I'm interested in the output.
All suggestions greatfully accepted. I've already run
Certainly is. Note that the space overwritten in the struct is probably a
string since the hex values spell out al/cvs_repository/tapest.
Just to confirm that one - the module in question was in
/usr/local/cvs_repository/tapestry ...
___
Info-cvs
[Red Hat 7.1, CVS 1.11.10]
I've been trying to check in a *big* change over pserver and getting some
nasty crashes from CVS (which unfortunately I did not take a note of -
System exit 11?). Eventually I discovered that this particular client
machine had an older version of CVS on it - 1.10.8
When I commit I'm also seeing:
Rlog: RCS/somefile: No such file or directory
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Jones [EMAIL PROTECTED] writes:
a) #cvs.lock - a directory (used when creating #cvs.[rw]fl.* locks)
b) #cvs.rfl.*.pid or #cvs.wfl.*.pid
c) ,file,
a's and b's but no c's.
Okay, if cvs core dumps you expect stale locks to be found in
I think that someone added a file to CVS in a way that didn't involve
typing the name of the file. People should really avoid naming files
with characters that are not printable ASCII. Theoretically it shouldn't
matter, but CVS is known to get indigestion when file names contain white
space.
Does the somefile exist in the repository, either in a container directory
or an Attic directory? I would expect something like this if someone rm's
an RCS (,v) file directly from the repository. Do other commands, such as
cvs status break with this file?
--- Forwarded mail from [EMAIL
And you are sure that there are no 'odd' files present in your
repository? (ls -alR) I think Redhat Linux allows UTF-8 characters in
filenames...
I'm afraid so. I did try an ls -b at the time; and wiping the sandbox and recopying
from my original tar made the problem go away.
Define 'large
12 matches
Mail list logo
