[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 'No such file or directoryctory' [sic] error
From: |
Alex Hunsley |
Subject: |
Re: 'No such file or directoryctory' [sic] error |
Date: |
Tue, 01 Mar 2005 23:24:01 GMT |
User-agent: |
Mozilla Thunderbird 0.9 (Windows/20041103) |
Matt Doar wrote:
IIRC, you can fix the error message by changing the default line ending
when you install/update cygwin. The actual cause of the error may well
be a permissions issue on the directory that is named. Take a look at
the repository for directories added without propagating their parent's
permission, and so not being group writeable.
~Matt
Hi Matt
thanks for that idea!
I can't find a way to change the default line ending in cygwin once it's
already installed (via the update) - AFAIK you only get offered the
option on first install...
Aside from that, if I type "mount" in cygwin I can see that everything
is mounted as binary mode, in which case it wouldn't do conversions anyway:
$ mount
C:\cygwin\bin on /usr/bin type system (binmode)
C:\cygwin\lib on /usr/lib type system (binmode)
C:\cygwin on / type system (binmode)
c: on /cygdrive/c type user (binmode,noumount)
d: on /cygdrive/d type user (binmode,noumount)
z: on /cygdrive/z type user (binmode,noumount)
(I'm sure I could find out how to change that though...)
I have managed to fix my problem since my first post with a quick hack -
turns out that the troublesome string is in the file /CVS/Repository
relative to the top directory of the module - this file has the name of
the module, 'dev', and <CR><LF> at the end of the line. Obviously the
cvs program considered <LF> to be the end-of-line and made <CR> part of
the string... so, to fix it, I ran a little util to convert this file to
UNIX line ending (i.e. it got rid of the <CR> aka 0x0d).
Now my commit works fine...!
So at least I know of a work around now... although obviously I'd rather
I didn't have to worry about a workaround. :/
thanks for your reply!
alex