public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: Gervase Markham <gerv@gerv.net>
Cc: cygwin@cygwin.com
Subject: Re: cvs package bug: cannot open val-tags file
Date: Fri, 23 Jul 2004 15:17:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.58.0407230849230.29341@slinky.cs.nyu.edu> (raw)
In-Reply-To: <4100C334.60705@gerv.net>

On Fri, 23 Jul 2004, Gervase Markham wrote:

> [Apologies if this is the wrong place for this bug report - cvshome.org
> is so impenetrable that I can't even search to see if this is an
> upstream cvs bug or not.]
>
> In Cygwin CVS 1.11.6-3 (but not 1.11.5-1 or 1.11.0-1), when trying to
> pull by tag, the following error is encountered:
>
> D:\mozilla>cvs -d //machine/share co -P -r NSPRPUB_PRE_4_2_CLIENT_BRANCH
> mozilla/nsprpub
> cvs checkout: warning: cannot open //machine/share/CVSROOT/val-tags
> read/write
> cvs [checkout aborted]: cannot read //machine/share/CVSROOT/val-tags
>
> Many other CVS operations (checkout, checkin, update) seem to work fine
> - it's only pulling by tag which fails.
>
> The repository in question is a copy of the Mozilla CVS repository,
> rsynced to a Win2K machine using Cygwin rsync and then SMB shared as
> readable and writable by all.
>
> The client machines we tried this on were running Win2K or Win2K3.
> CVSROOT was "//machine/sharepoint" when we didn't specify it on the
> command line. CYGWIN was set to "nontsec". The machine can cat and touch
> the val-tags file on the share - it seems that only the CVS process
> cannot see it correctly.
>
> We solved the issue by downgrading CVS to 1.11.5-1 using the Cygwin
> setup.exe, so the problem is not urgent for us.
>
> If more information is required, please ask. I'm subscribed to the
> digest version of the list, so it may take a day or two to get a response.
>
> Many thanks for your time,
> Gerv

Gerv,

I wonder if it's related to CVS's inability to remove lock directories
from some SMB shares, which I reported back in 2003...  That seems to be
hard to track, because different SMB shares have subtly different access
settings.  In any case, first try adding "nosmbntsec" to your $CYGWIN, and
see if it helps.  I also found that, when using Samba from AIX (don't know
about Linux/Windows), it helps to add the group that owns the repository
to /etc/group, and add the Cygwin user to that group.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

      reply	other threads:[~2004-07-23 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 11:02 Gervase Markham
2004-07-23 15:17 ` Igor Pechtchanski [this message]

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=Pine.GSO.4.58.0407230849230.29341@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin@cygwin.com \
    --cc=gerv@gerv.net \
    /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).