From: Mark Levedahl <mlevedahl@gmail.com>
To: cygwin@cygwin.com
Subject: problem with cvs binary?
Date: Tue, 16 Jul 2013 06:03:00 -0000 [thread overview]
Message-ID: <ks2e8i$idp$1@ger.gmane.org> (raw)
The currently provided cvs executable does not work correctly, simple
test case is:
~>export CVSROOT=/tmp/cvsroot
~>cvs init
~>cvs co -d /tmp/workdir .
cvs [checkout aborted]: cannot make directory : No such file or directory
~>cygcheck -c cvs
Cygwin Package Information
Package Version Status
cvs 1.12.13-10 OK
~>uname -a
CYGWIN_NT-5.1 virt-winxp 1.7.20(0.266/5/3) 2013-06-07 11:11 i686 Cygwin
The above should checkout the empty project to /tmp/workdir, but does
not work with the binary provided via setup.exe. This does work
correctly with a) cvs-1.12.13 rebuilt from sources, and b) with cvs v
1.11.22-1 downloaded from setup.exe. The expected result:
~>cygcheck -c cvs
Cygwin Package Information
Package Version Status
cvs 1.11.22-1 OK
~>cvs co -d /tmp/work .
cvs checkout: Updating /tmp/work
cvs checkout: Updating /tmp/work/CVSROOT
U /tmp/work/CVSROOT/checkoutlist
U /tmp/work/CVSROOT/commitinfo
U /tmp/work/CVSROOT/config
U /tmp/work/CVSROOT/cvswrappers
U /tmp/work/CVSROOT/editinfo
U /tmp/work/CVSROOT/loginfo
U /tmp/work/CVSROOT/modules
U /tmp/work/CVSROOT/notify
U /tmp/work/CVSROOT/rcsinfo
U /tmp/work/CVSROOT/taginfo
U /tmp/work/CVSROOT/verifymsg
Mark
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2013-07-16 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 6:03 Mark Levedahl [this message]
2013-07-16 13:30 ` Charles Wilson
2013-07-16 15:01 ` Corinna Vinschen
2013-07-16 15:52 ` mingw.org cross compiler [Was: problem with cvs binary?] Charles Wilson
2013-07-16 17:05 ` Earnie Boyd
2013-07-17 1:39 ` Charles Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ks2e8i$idp$1@ger.gmane.org' \
--to=mlevedahl@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).