public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: AnonCVS problem
Date: Thu, 26 Aug 2004 17:38:00 -0000	[thread overview]
Message-ID: <412E1FFE.7030708@eCosCentric.com> (raw)
In-Reply-To: <1093540557.2961.2902.camel@hermes>

Gary Thomas wrote:
> On Thu, 2004-08-26 at 11:00, Jonathan Larmour wrote:
> 
>>Gary Thomas wrote:
>>
>>>I have a checkout of the anonymous CVS that I'm trying to update.  Lots of
>>>issues though:
>>>
>>>[gthomas@hermes ecos]$ cvs -q up -d -P
>>>cvs update: warning: cannot write to history file /cvs/ecos/CVSROOT/history: Permission denied
>>>P doc/ChangeLog
>>>RCS file: /cvs/ecos/ecos/doc/sgml/doclist,v
>>>retrieving revision 1.14
>>>retrieving revision 1.16
>>>Merging differences between 1.14 and 1.16 into doclist
>>>M doc/sgml/doclist
>>>cvs update: warning: cannot write to history file /cvs/ecos/CVSROOT/history: Permission denied
>>>cvs update: warning: cannot write to history file /cvs/ecos/CVSROOT/history: Permission denied
>>>P doc/sgml/makemakefile
>>>cvs update: warning: cannot write to history file /cvs/ecos/CVSROOT/history: Permission denied
>>>
>>>Any ideas what's up with this?
>>
>>I've just tried it and it works for me. On sourceware, the permissions look 
>>sensible:
>>
>>-rw-rw-r--    1 jlarmour ecos     92450589 Aug 26 16:41 history
>>
>>And I've just confirmed you are still in group ecos.
>>
>>So either it's already been fixed or there's other weirdness. Perhaps check 
>>your CVS/Root in those directories just in case (including e.g. ssh, not 
>>pserver)?
> 
> 
> No, I'm trying to use the pserver interface - that's what my customers 
> need.  I'm fine for my own SSH use.

It should be fixed now. It was a consequence of a different change on 
sourceware to remote the anoncvs user from project groups.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

      reply	other threads:[~2004-08-26 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 15:34 Gary Thomas
2004-08-26 17:00 ` Jonathan Larmour
2004-08-26 17:16   ` Gary Thomas
2004-08-26 17:38     ` Jonathan Larmour [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=412E1FFE.7030708@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=gary@mlbassoc.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).