public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: Mo DeJong <mdejong@cygnus.com>
Cc: overseers@sources.redhat.com
Subject: Re: SSH key reinit
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <20001018234222.H15926@cygnus.com> (raw)
In-Reply-To: <Pine.SOL.3.91.1001018202239.18466D-100000@cse.cygnus.com>

On Wed, Oct 18, 2000 at 08:31:28PM -0700, Mo DeJong wrote:
>On Wed, 18 Oct 2000, Jeffrey A Law wrote:
>
>>   In message < Pine.SOL.3.91.1001018143808.16582B-100000@cse.cygnus.com >you writ
>> e:
>>   > If I wanted to get my ssh key reset on sourceware
>>   > so that I can check a patch into the itcl module,
>>   > would I just send the public key in?
>>
>> Yup.  I've installed it.  Do you want me to zap your old key?
>> 
>> jeff
> 
>Yes please.
>
>I tested it out with the new key, but something seems
>to be wrong with my permissions.
>
>% cvs commit ChangeLog itcl/generic/itcl_objects.c 
>cvs [server aborted]: "commit" requires write access to the repository
>
>This worked before, could the change of ssh keys have something
>to do with this?

You do seem to have the write group access on sourceware.  Are you sure that
you are using SSH to access the repository and not anoncvs or something?

cgf

WARNING: multiple messages have this Message-ID
From: Christopher Faylor <cgf@redhat.com>
To: Mo DeJong <mdejong@cygnus.com>
Cc: overseers@sources.redhat.com
Subject: Re: SSH key reinit
Date: Wed, 18 Oct 2000 20:42:00 -0000	[thread overview]
Message-ID: <20001018234222.H15926@cygnus.com> (raw)
Message-ID: <20001018204200.5uunQNkB3h-9h0g4YnS6XEl7qsZZq8vReeo-T8MCGeE@z> (raw)
In-Reply-To: <Pine.SOL.3.91.1001018202239.18466D-100000@cse.cygnus.com>

On Wed, Oct 18, 2000 at 08:31:28PM -0700, Mo DeJong wrote:
>On Wed, 18 Oct 2000, Jeffrey A Law wrote:
>
>>   In message < Pine.SOL.3.91.1001018143808.16582B-100000@cse.cygnus.com >you writ
>> e:
>>   > If I wanted to get my ssh key reset on sourceware
>>   > so that I can check a patch into the itcl module,
>>   > would I just send the public key in?
>>
>> Yup.  I've installed it.  Do you want me to zap your old key?
>> 
>> jeff
> 
>Yes please.
>
>I tested it out with the new key, but something seems
>to be wrong with my permissions.
>
>% cvs commit ChangeLog itcl/generic/itcl_objects.c 
>cvs [server aborted]: "commit" requires write access to the repository
>
>This worked before, could the change of ssh keys have something
>to do with this?

You do seem to have the write group access on sourceware.  Are you sure that
you are using SSH to access the repository and not anoncvs or something?

cgf

  parent reply	other threads:[~2000-12-30  6:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Mo DeJong
2000-10-18 14:41 ` Mo DeJong
2000-12-30  6:08 ` Jeffrey A Law
2000-10-18 20:04   ` Jeffrey A Law
2000-12-30  6:08   ` Mo DeJong
2000-10-18 20:31     ` Mo DeJong
2000-12-30  6:08     ` Christopher Faylor [this message]
2000-10-18 20:42       ` Christopher Faylor
2000-12-30  6:08       ` Mo DeJong
2000-10-18 21:33         ` Mo DeJong
2000-12-30  6:08     ` Jeffrey A Law
2000-10-18 20:41       ` Jeffrey A Law

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=20001018234222.H15926@cygnus.com \
    --to=cgf@redhat.com \
    --cc=mdejong@cygnus.com \
    --cc=overseers@sources.redhat.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).