Bug Report: CVS often fails in scripts under Cygwin

Bug Report: CVS often fails in scripts under Cygwin

[Josh Schulte]

When I use CVS in scripts under Cygwin I often get "cvs: permission denied".
This happens in perl and shell scripts. Not every cvs command will fail. But
the ones that fail seem to consistently fail. For instance the following
script:

#!/bin/sh
cvs edit build.txt
echo "test" > build.txt
cvs commit -m test build.txt

gives the following output:

cvs: permission denied
cvs: permission denied

I ran this on Solaris to verify that I wasn't missing something, and of
course it worked.

I've included my configuration information below.

*********************************************************

Cygnus Win95/NT Configuration Diagnostics
Current System Time: Wed Sep 20 15:30:41 2000

WinNT Ver 5.0 build 2195 

Path:	.
	/usr/local/bin
	/usr/local/bin
	/bin
	/c/development/Tools/common/bin
	/c/WINNT/system32
	/c/WINNT

SysDir: C:\WINNT\System32
WinDir: C:\WINNT

HOME = `/c/Documents and Settings/Josh_Schulte'
PWD = `/eq/dev'
USER = `josh_schulte'

!C: = `C:\development\Tools\win386\usr_local\bin'
ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
APPDATA = `C:\Documents and Settings\Josh_Schulte\Application Data'
BUILD_INSTALLED = `/eq/dev/_Installed'
BUILD_OUTPUT = `/eq/dev/_Output'
BUILD_ROOT = `/eq/dev'
BUILD_THIRDPARTY = `/c/development/Devel/../ThirdParty'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
COMPUTERNAME = `EQ5386JS'
COMSPEC = `C:\WINNT\system32\cmd.exe'
CVSROOT = `:pserver:josh_schulte@eqcvs.equilibrium.com:/home/cvs/cvsroot'
EDITOR = `u2w --double --exec /usr/local/pkg/textpad/textpad'
GROUP = `Administrators'
HOMEDRIVE = `C:'
HOMEPATH = `\'
HOST = `EQ5386JS'
HOSTTYPE = `i386'
INCLUDE = `C:\Program Files\Microsoft Visual
Studio\VC98\atl\include;C:\Program Files\Microsoft Visual
Studio\VC98\mfc\include;C:\Program Files\Microsoft Visual
Studio\VC98\include'
LIB = `C:\Program Files\Microsoft Visual Studio\VC98\mfc\lib;C:\Program
Files\Microsoft Visual Studio\VC98\lib'
LOGNAME = `josh_schulte'
LOGONSERVER = `\\OFFSITESERV'
MACHTYPE = `i386'
MSDEVDIR = `C:\Program Files\Microsoft Visual Studio\Common\MSDev98'
NUMBER_OF_PROCESSORS = `1'
OS2LIBPATH = `C:\WINNT\system32\os2\dll;'
OS = `Windows_NT'
OSTYPE = `posix'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 6 Model 8 Stepping 1, GenuineIntel'
PROCESSOR_LEVEL = `6'
PROCESSOR_REVISION = `0801'
PROGRAMFILES = `C:\Program Files'
PROMPT = `$P$G'
SHLVL = `1'
SYSTEMDRIVE = `C:'
SYSTEMROOT = `C:\WINNT'
TEMP = `C:\DOCUME~1\JOSH_S~1\LOCALS~1\Temp'
TERM = `cygwin'
TMP = `C:\DOCUME~1\JOSH_S~1\LOCALS~1\Temp'
TMPDIR = `/tmp'
TZ = `PST8PDT7,M4.1.0/2,M10.5.0/2'
USERDNSDOMAIN = `equildom.equilibrium.com'
USERDOMAIN = `EQUILDOM'
USERNAME = `josh_schulte'
USERPROFILE = `C:\Documents and Settings\Josh_Schulte'
VENDOR = `intel'
VISUAL = `u2w --double --exec /usr/local/pkg/textpad/textpad -m'
WINDIR = `C:\WINNT'
WINNT = `/c/WINNT'

HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
  (default) = `/cygdrive'
  cygdrive flags = 0x00000020
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/
  (default) = `C:\development\Tools\win386\cygwin'
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/c
  (default) = `c:'
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/d
  (default) = `d:'
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/eq/devtree
  (default) = `C:\development\Tools\..'
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/local
  (default) = `C:\development\Tools\win386\usr_local'
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2

a:  fd           N/A    N/A                    
b:  net NTFS   95942Mb  29% CP CS UN PA FC     Development
c:  hd  NTFS    8683Mb  51% CP CS UN PA FC     HARD_DRIVE
d:  cd           N/A    N/A                    
g:  net NTFS   95942Mb  29% CP CS UN PA FC     Development
o:  net NTFS   91847Mb  14% CP CS UN PA FC     files
p:  net NTFS   95942Mb  29% CP CS UN PA FC     Development
u:  net NTFS   91847Mb  52% CP CS UN PA FC     files
x:  net NTFS   20434Mb  84% CP CS UN PA FC     

C:\development\Tools\win386\usr_local  /usr/local  user    textmode
C:\development\Tools\win386\cygwin  /        user    textmode
C:\development\Tools\..  /eq/devtree  user    textmode
c:    /c       user    textmode
d:    /d       user    textmode

Found: C:\development\Tools\win386\cygwin\bin\bash.exe
Found: C:\development\Tools\win386\cygwin\bin\cat.exe
Found: C:\development\Tools\win386\cygwin\bin\cpp.exe
Found: C:\development\Tools\win386\cygwin\bin\find.exe
Found: C:\development\Tools\win386\cygwin\bin\gcc.exe
Found: C:\development\Tools\win386\cygwin\bin\gdb.exe
Found: C:\development\Tools\win386\cygwin\bin\ld.exe
Found: C:\development\Tools\win386\cygwin\bin\ls.exe
Found: C:\development\Tools\win386\cygwin\bin\make.exe
Found: C:\development\Tools\win386\cygwin\bin\sh.exe

  115k 2000/04/24 C:\development\Tools\win386\cygwin\bin\cygitcl30.dll -
os=4.0 img=1.0 sys=4.0
                  "cygitcl30.dll" v0.0 ts=1999/9/13 19:46
   63k 2000/04/24 C:\development\Tools\win386\cygwin\bin\cygitk30.dll -
os=4.0 img=1.0 sys=4.0
                  "cygitk30.dll" v0.0 ts=1999/9/13 19:47
  474k 2000/04/24 C:\development\Tools\win386\cygwin\bin\cygtcl80.dll -
os=4.0 img=1.0 sys=4.0
                  "cygtcl80.dll" v0.0 ts=1999/9/13 19:31
   19k 2000/04/24 C:\development\Tools\win386\cygwin\bin\cygtclpip80.dll -
os=4.0 img=1.0 sys=4.0
   24k 2000/04/24 C:\development\Tools\win386\cygwin\bin\cygtclreg80.dll -
os=4.0 img=1.0 sys=4.0
                  "cygtclreg80.dll" v0.0 ts=1999/9/13 19:31
  768k 2000/04/24 C:\development\Tools\win386\cygwin\bin\cygtk80.dll -
os=4.0 img=1.0 sys=4.0
                  "cygtk80.dll" v0.0 ts=1999/9/13 19:36
  587k 2000/04/24 C:\development\Tools\win386\cygwin\bin\cygwin1.dll -
os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2000/2/29 21:15
Use -h to see help about each section

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Bug Report: CVS often fails in scripts under Cygwin

[Charles Wilson]

Josh Schulte wrote:
> 
> When I use CVS in scripts under Cygwin I often get "cvs: permission denied".
> This happens in perl and shell scripts. Not every cvs command will fail. But
> the ones that fail seem to consistently fail. For instance the following
> script:
> 
> #!/bin/sh
> cvs edit build.txt
> echo "test" > build.txt
> cvs commit -m test build.txt
> 
> gives the following output:
> 
> cvs: permission denied
> cvs: permission denied
> 
> I ran this on Solaris to verify that I wasn't missing something, and of
> course it worked.
> 

Can you run these three commands from the shell by hand without error?

$ cvs edit build.txt
$ echo "test" > build.txt
$ cvs commit -m test build.txt

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Bug Report: CVS often fails in scripts under Cygwin

[S.Yoshida]

Josh Schulte <jschulte@equilibrium.com> wrote:
> 
> cvs: permission denied
> cvs: permission denied
> 
> I ran this on Solaris to verify that I wasn't missing something, and of
> course it worked.
> 
> I've included my configuration information below.
> 

I could not build perl under new Cygwin.
 dllwrap success in prompt. / dllwrap failed in perlld script.

AND, :-(   I found bug in 1.1.5 script.

BASH$pwd
/usr/local/src

BASH$cat script
#!/bin/sh
echo $0

BASH$sh ./script
./script

BASH$./script
c:/cygwin/usr/local/src/script

So, ./configure failed, Can't make cygwin1.dll any more :-(

-- 
Best Regards, 
S.Yoshida

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Bug Report: CVS often fails in scripts under Cygwin

[Charles S. Wilson]

"S.Yoshida" wrote:
> 
> I could not build perl under new Cygwin.
>  dllwrap success in prompt. / dllwrap failed in perlld script.

And what, exactly, does this have to do with CVS?  In any case, I just
built perl the other day on cygwin.  And posted the necessary patches to
the list (there are some patches to perl-5.6.0 that are required by
newer (1.1.3+) cygwin's.

> 
> AND, :-(   I found bug in 1.1.5 script.

There ain't no such animal.  1.1.5 has not been released, and will not
be released until it's ready.  You must be talking about development
snapshots.

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Bug Report: CVS often fails in scripts under Cygwin

[Josh Schulte]

Chuck,

Yes, it does work from the command line. In fact I have made extensive use
cvs from the command line. cvs is only giving me problems when I use if from
a script.

Thanks,
Josh

> > When I use CVS in scripts under Cygwin I often get "cvs: 
> permission denied".
> > This happens in perl and shell scripts. Not every cvs 
> command will fail. But
> > the ones that fail seem to consistently fail. For instance 
> the following
> > script:

> Can you run these three commands from the shell by hand without error?
> 
> $ cvs edit build.txt
> $ echo "test" > build.txt
> $ cvs commit -m test build.txt

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Bug Report: CVS often fails in scripts under Cygwin

[Earnie Boyd]

--- Josh Schulte <jschulte@equilibrium.com> wrote:
> When I use CVS in scripts under Cygwin I often get "cvs: permission denied".
> This happens in perl and shell scripts. Not every cvs command will fail. But
> the ones that fail seem to consistently fail. For instance the following
> script:
> 
> #!/bin/sh
> cvs edit build.txt
> echo "test" > build.txt
> cvs commit -m test build.txt
> 
> gives the following output:
> 
> cvs: permission denied
> cvs: permission denied
> 
> I ran this on Solaris to verify that I wasn't missing something, and of
> course it worked.
> 
> I've included my configuration information below.
> 
> *********************************************************
> 
> Cygnus Win95/NT Configuration Diagnostics
> Current System Time: Wed Sep 20 15:30:41 2000
> 
> WinNT Ver 5.0 build 2195 
> 
> Path:	.
> 	/usr/local/bin
> 	/usr/local/bin
> 	/bin
> 	/c/development/Tools/common/bin
> 	/c/WINNT/system32
> 	/c/WINNT
> 
> SysDir: C:\WINNT\System32
> WinDir: C:\WINNT
> 
> HOME = `/c/Documents and Settings/Josh_Schulte'
> PWD = `/eq/dev'
> USER = `josh_schulte'
> 

Your HOME has spaces in it.  I suggest that you:
  mkdir /home
  mount c:/Documents\ and\ Settings /home
  export HOME=/home/Josh_Schulte
This may or may not solve your problem.

Cheers,

=====
--- < http://earniesystems.safeshopper.com > ---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Bug Report: CVS often fails in scripts under Cygwin

[Josh Schulte]

S.

You should be able to verify this bug with sh too.

Thanks,
Josh

-----Original Message-----
From: vzy03312@ha.bekkoame.ne.jp [ mailto:vzy03312@ha.bekkoame.ne.jp ]
Sent: Thursday, September 21, 2000 11:04 AM
To: cygwin@sourceware.cygnus.com
Subject: Re: Bug Report: CVS often fails in scripts under Cygwin


Josh Schulte <jschulte@equilibrium.com> wrote:
> 
> cvs: permission denied
> cvs: permission denied
> 
> I ran this on Solaris to verify that I wasn't missing something, and of
> course it worked.
> 
> I've included my configuration information below.
> 

I could not build perl under new Cygwin.
 dllwrap success in prompt. / dllwrap failed in perlld script.

AND, :-(   I found bug in 1.1.5 script.

BASH$pwd
/usr/local/src

BASH$cat script
#!/bin/sh
echo $0

BASH$sh ./script
./script

BASH$./script
c:/cygwin/usr/local/src/script

So, ./configure failed, Can't make cygwin1.dll any more :-(

-- 
Best Regards, 
S.Yoshida

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Bug Report: CVS often fails in scripts under Cygwin

[Earnie Boyd]

--- Josh Schulte <jschulte@equilibrium.com> wrote:
> 
> My home is set to /home/Josh_Schulte and I am still getting the "permission
> denied" crap.
> 

I noticed that you had told Chuck that you could do the steps of the script
interactively.  Have you checked for \r\n line endings in the script file?

Cheers,

=====
--- < http://earniesystems.safeshopper.com > ---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Bug Report: CVS often fails in scripts under Cygwin

[Josh Schulte]

Do I or do I not want \r\n? I wrote the scripts in windows so the shell
script will have them. What is a good way to double check. I am not sure
what perl does when it sends the commands to the shell (\r\n or just \n) it
starts with system().

Josh

-----Original Message-----
From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
Sent: Thursday, September 21, 2000 11:42 AM
To: Josh Schulte
Cc: cygwin users
Subject: RE: Bug Report: CVS often fails in scripts under Cygwin


--- Josh Schulte <jschulte@equilibrium.com> wrote:
> 
> My home is set to /home/Josh_Schulte and I am still getting the
"permission
> denied" crap.
> 

I noticed that you had told Chuck that you could do the steps of the script
interactively.  Have you checked for \r\n line endings in the script file?

Cheers,

=====
--- < http://earniesystems.safeshopper.com > ---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Bug Report: CVS often fails in scripts under Cygwin

[Earnie Boyd]

--- Josh Schulte <jschulte@equilibrium.com> wrote:
> 
> Do I or do I not want \r\n? I wrote the scripts in windows so the shell
> script will have them. What is a good way to double check. I am not sure
> what perl does when it sends the commands to the shell (\r\n or just \n) it
> starts with system().
> 

Well since cvs is trying to open a file name foo\r and since foo\r is an
illegal filename for Win32; then, you don't want \r\n line endings.  Have you
updated you Cygwin recently?  IIRC, both ash and bash were modified to read
script files in text mode so that these problems don't occur.

To modify your file you can:
  cp foo.sh foo.tmp
  tr -d '\r' < foo.tmp > foo.sh
  rm foo.tmp

This will delete all \r's in the file.

Cheers,

=====
--- < http://earniesystems.safeshopper.com > ---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Bug Report: CVS often fails in scripts under Cygwin

[Josh Schulte]

Chuck,

Have you written any scripts using cvs? Can you verify this on your setup?
It may take a couple of different approaches because not every cvs command
will give the
"permission denied". Some scripts work just fine.
 
Another guy here at work gets the same results. So if you or someone else is
not getting this problem, then it is probably something we have setup in our
environment.

Thanks,
Josh

-----Original Message-----
From: Josh Schulte 
Sent: Wednesday, September 20, 2000 4:59 PM
To: 'Charles Wilson'; Josh Schulte
Cc: 'cygwin@sourceware.cygnus.com'
Subject: RE: Bug Report: CVS often fails in scripts under Cygwin


Chuck,

Yes, it does work from the command line. In fact I have made extensive use
cvs from the command line. cvs is only giving me problems when I use if from
a script.

Thanks,
Josh

> > When I use CVS in scripts under Cygwin I often get "cvs: 
> permission denied".
> > This happens in perl and shell scripts. Not every cvs 
> command will fail. But
> > the ones that fail seem to consistently fail. For instance 
> the following
> > script:

> Can you run these three commands from the shell by hand without error?
> 
> $ cvs edit build.txt
> $ echo "test" > build.txt
> $ cvs commit -m test build.txt

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Bug Report: CVS often fails in scripts under Cygwin

[Charles S. Wilson]

Josh Schulte wrote:
> 
> Chuck,
> 
> Have you written any scripts using cvs? Can you verify this on your setup?
> It may take a couple of different approaches because not every cvs command
> will give the
> "permission denied". Some scripts work just fine.

No, I only use cvs manually.  Also, since I only use it for "personal"
projects on my own machine -- not shared projects -- I don't use
'reserved checkouts' (e.g. cvs watch, cvs edit, cvs unedit, etc).

> Another guy here at work gets the same results. So if you or someone else is
> not getting this problem, then it is probably something we have setup in our
> environment.

Okay, I set up a test repository 'foo' with one file.  Seems to work
fine here.

mkdir foo
cd foo
touch build.txt
cvs import -m "test module" foo foo_1 foo_1_00
cd ..
cvs watch on
rm -rf foo
cvs checkout foo
cd foo

---- Okay, so module foo has one empty file called "build.txt". Now,
create the following script (use /bin/sh -x so we can trace execution)

--- 'test' ----
#!/bin/sh -x
cvs edit build.txt
echo "test" $1 > build.txt
cvs commit -m "test" build.txt
cvs unedit build.txt
--- 'test' ----

chmod +x test
./test 1

---output is----
+ cvs edit build.txt
+ echo test 1
+ cvs commit -m test build.txt
Checking in build.txt;
/e/Users/cwilson/.cvsroot/foo/build.txt,v  <--  build.txt
new revision: 1.3; previous revision: 1.2
done
+ cvs unedit build.txt
----end----

Notes: running under WinNT, repository and checkout dir are both on NTFS
drives.  Looks like your problem is somehow related to your setup. :-(

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Bug Report: CVS often fails in scripts under Cygwin

[Josh Schulte]

Chuck,

Are you on win2k or nt 4?

Thanks,
Josh

-----Original Message-----
From: Charles S. Wilson [ mailto:cwilson@ece.gatech.edu ]
Sent: Thursday, September 21, 2000 12:29 PM
To: Josh Schulte
Cc: 'cygwin@sourceware.cygnus.com'
Subject: Re: Bug Report: CVS often fails in scripts under Cygwin


Josh Schulte wrote:
> 
> Chuck,
> 
> Have you written any scripts using cvs? Can you verify this on your setup?
> It may take a couple of different approaches because not every cvs command
> will give the
> "permission denied". Some scripts work just fine.

No, I only use cvs manually.  Also, since I only use it for "personal"
projects on my own machine -- not shared projects -- I don't use
'reserved checkouts' (e.g. cvs watch, cvs edit, cvs unedit, etc).

> Another guy here at work gets the same results. So if you or someone else
is
> not getting this problem, then it is probably something we have setup in
our
> environment.

Okay, I set up a test repository 'foo' with one file.  Seems to work
fine here.

mkdir foo
cd foo
touch build.txt
cvs import -m "test module" foo foo_1 foo_1_00
cd ..
cvs watch on
rm -rf foo
cvs checkout foo
cd foo

---- Okay, so module foo has one empty file called "build.txt". Now,
create the following script (use /bin/sh -x so we can trace execution)

--- 'test' ----
#!/bin/sh -x
cvs edit build.txt
echo "test" $1 > build.txt
cvs commit -m "test" build.txt
cvs unedit build.txt
--- 'test' ----

chmod +x test
./test 1

---output is----
+ cvs edit build.txt
+ echo test 1
+ cvs commit -m test build.txt
Checking in build.txt;
/e/Users/cwilson/.cvsroot/foo/build.txt,v  <--  build.txt
new revision: 1.3; previous revision: 1.2
done
+ cvs unedit build.txt
----end----

Notes: running under WinNT, repository and checkout dir are both on NTFS
drives.  Looks like your problem is somehow related to your setup. :-(

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Bug Report: CVS often fails in scripts under Cygwin

[Charles S. Wilson]

Both.  However, I ran the tests below on my NT4.0sp6a box.

--Chuck

Josh Schulte wrote:
> 
> Chuck,
> 
> Are you on win2k or nt 4?
> 
> Thanks,
> Josh
> 
> -----Original Message-----
> From: Charles S. Wilson [ mailto:cwilson@ece.gatech.edu ]
> Sent: Thursday, September 21, 2000 12:29 PM
> To: Josh Schulte
> Cc: 'cygwin@sourceware.cygnus.com'
> Subject: Re: Bug Report: CVS often fails in scripts under Cygwin
> 
> Josh Schulte wrote:
> >
> > Chuck,
> >
> > Have you written any scripts using cvs? Can you verify this on your setup?
> > It may take a couple of different approaches because not every cvs command
> > will give the
> > "permission denied". Some scripts work just fine.
> 
> No, I only use cvs manually.  Also, since I only use it for "personal"
> projects on my own machine -- not shared projects -- I don't use
> 'reserved checkouts' (e.g. cvs watch, cvs edit, cvs unedit, etc).
> 
> > Another guy here at work gets the same results. So if you or someone else
> is
> > not getting this problem, then it is probably something we have setup in
> our
> > environment.
> 
> Okay, I set up a test repository 'foo' with one file.  Seems to work
> fine here.
> 
> mkdir foo
> cd foo
> touch build.txt
> cvs import -m "test module" foo foo_1 foo_1_00
> cd ..
> cvs watch on
> rm -rf foo
> cvs checkout foo
> cd foo
> 
> ---- Okay, so module foo has one empty file called "build.txt". Now,
> create the following script (use /bin/sh -x so we can trace execution)
> 
> --- 'test' ----
> #!/bin/sh -x
> cvs edit build.txt
> echo "test" $1 > build.txt
> cvs commit -m "test" build.txt
> cvs unedit build.txt
> --- 'test' ----
> 
> chmod +x test
> ./test 1
> 
> ---output is----
> + cvs edit build.txt
> + echo test 1
> + cvs commit -m test build.txt
> Checking in build.txt;
> /e/Users/cwilson/.cvsroot/foo/build.txt,v  <--  build.txt
> new revision: 1.3; previous revision: 1.2
> done
> + cvs unedit build.txt
> ----end----
> 
> Notes: running under WinNT, repository and checkout dir are both on NTFS
> drives.  Looks like your problem is somehow related to your setup. :-(
> 
> --Chuck
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Bug Report: CVS often fails in scripts under Cygwin

[Earnie Boyd]

--- Josh Schulte <jschulte@equilibrium.com> wrote:
> Chuck,
> 
> Are you on win2k or nt 4?
> 

Why does this matter?  You and I have already determined, hours ago, that your
problem with the script is \r\n line endings.

Cheers,

=====
--- < http://earniesystems.safeshopper.com > ---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://gw32.freeyellow.com/ >
           __Minimalist GNU for Windows__
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Bug Report: CVS often fails in scripts under Cygwin

[Josh Schulte]

You determined it? You recreated the "permission denied" on your system, the
got the script to work by removing the \r's?

I found that that wasn't the problem. If I remove the /r's the cvs commands
still fail.

I droped the latest cygwin and bash over my current setup and that didn't
fix it either.

Thanks,
Josh

-----Original Message-----
From: Earnie Boyd [ mailto:earnie_boyd@yahoo.com ]
Sent: Thursday, September 21, 2000 4:31 PM
To: Josh Schulte; 'Charles S. Wilson'
Cc: 'cygwin@sourceware.cygnus.com'
Subject: RE: Bug Report: CVS often fails in scripts under Cygwin


--- Josh Schulte <jschulte@equilibrium.com> wrote:
> Chuck,
> 
> Are you on win2k or nt 4?
> 

Why does this matter?  You and I have already determined, hours ago, that
your
problem with the script is \r\n line endings.

****************************************************************************
*

Well since cvs is trying to open a file name foo\r and since foo\r is an
illegal filename for Win32; then, you don't want \r\n line endings.  Have
you
updated you Cygwin recently?  IIRC, both ash and bash were modified to read
script files in text mode so that these problems don't occur.

To modify your file you can:
  cp foo.sh foo.tmp
  tr -d '\r' < foo.tmp > foo.sh
  rm foo.tmp

This will delete all \r's in the file.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com