From: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
To: Ian Lance Taylor <ian@airs.com>
Cc: overseers@gcc.gnu.org
Subject: Re: not able to access svn+ssh for gcc
Date: Thu, 18 Dec 2014 12:44:00 -0000 [thread overview]
Message-ID: <CAAgBjM=YQMyJoCkfevwGLXdk=AEF-mhiyHTHSeOgZBZf3ZpQgA@mail.gmail.com> (raw)
In-Reply-To: <m3bnn1lgbv.fsf@pepe.airs.com>
On 18 December 2014 at 10:11, Ian Lance Taylor <ian@airs.com> wrote:
> Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org> writes:
>
>> I recently got write access to gcc svn trunk (prathamesh3492@gcc.gnu.org).
>> When I try to access svn,
>> with svn ls svn+ssh://prathamesh3492@gcc.gnu.org/svn/gcc
>> I get following error:
>> Permission denied (publickey).
>> svn: E210002: Unable to connect to a repository at URL
>> 'svn+ssh://prathamesh3492@gcc.gnu.org/svn/gcc'
>> svn: E210002: To better debug SSH connection problems, remove the -q
>> option from 'ssh' in the [tunnels] section of your Subversion
>> configuration file.
>> svn: E210002: Network connection closed unexpectedly
>>
>> svn ls svn://gcc.gnu.org/svn/gcc works fine (similarly for other svn commands).
>> I have the same id_rsa.pub (attached) in my .ssh directory as the one
>> I uploaded.
>
> The file you attached is not the one on sourceware. The one on
> sourceware has the same "bilbo@bilbo-Ideapad-Z560" identifier but has
> different contents.
Indeed. I am now able to access svn+ssh. Sorry for the noise.
Regards,
Prathamesh
>
> Ian
prev parent reply other threads:[~2014-12-18 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 7:50 Prathamesh Kulkarni
2014-12-18 7:58 ` Ian Lance Taylor
2014-12-18 12:44 ` Prathamesh Kulkarni [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='CAAgBjM=YQMyJoCkfevwGLXdk=AEF-mhiyHTHSeOgZBZf3ZpQgA@mail.gmail.com' \
--to=prathamesh.kulkarni@linaro.org \
--cc=ian@airs.com \
--cc=overseers@gcc.gnu.org \
/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).