From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 130514 invoked by alias); 22 Apr 2019 14:27:04 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 130506 invoked by uid 89); 22 Apr 2019 14:27:04 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=4.1 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SCAM_SUBJECT,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 spammy=Recently, helping, HTo:U*cgf-use-the-mailinglist-please, U*overseers X-HELO: APC01-PU1-obe.outbound.protection.outlook.com Received: from mail-oln040092254082.outbound.protection.outlook.com (HELO APC01-PU1-obe.outbound.protection.outlook.com) (40.92.254.82) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 22 Apr 2019 14:27:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=qLl1W+nuKsyDReyB9MWjebMXc5Bbokyc+2s6Y8EBsZo=; b=GaYFD9gmAKf0ara5EF+OhcQxGbCMfI9r2HykkcA8T//I01qINIDfJOD5/Kj9TStO5as6j09ImUJfzqaBpu8/wTi1WOCH2quAmkF25mYlzvH9SwJXXsYylxHHjCMpnjuDxoPbMS1tb+XO3m5V8L3CyU2idwAgDF8r3dSj+p/ds+ogwDq1Qqum3TtbkmV6zLRwpFrFBnkxKEbz1O23ikjlk7myjfG22tceeo6cWsx+Wkpr2/jbfSuEm3Gv8DISL2oQRP/EH1h6jeopEoo26NOKoK6NWS0LTkHQdEwoFfjpFpE/lV5Jmmy4ENQeVL2I/cbe+YA3nyobIKV49xFsKrNr2A== Received: from SG2APC01FT020.eop-APC01.prod.protection.outlook.com (10.152.250.59) by SG2APC01HT185.eop-APC01.prod.protection.outlook.com (10.152.251.234) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1771.16; Mon, 22 Apr 2019 14:26:58 +0000 Received: from HK0PR02MB2897.apcprd02.prod.outlook.com (10.152.250.58) by SG2APC01FT020.mail.protection.outlook.com (10.152.250.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1771.16 via Frontend Transport; Mon, 22 Apr 2019 14:26:58 +0000 Received: from HK0PR02MB2897.apcprd02.prod.outlook.com ([fe80::e1f9:6a4d:bf9e:8ce5]) by HK0PR02MB2897.apcprd02.prod.outlook.com ([fe80::e1f9:6a4d:bf9e:8ce5%4]) with mapi id 15.20.1813.017; Mon, 22 Apr 2019 14:26:58 +0000 From: ben narwal To: Christopher Faylor CC: "overseers@gcc.gnu.org" Subject: Re: Question about write-access svn repository of my account Date: Mon, 22 Apr 2019 14:27:00 -0000 Message-ID: References: ,<20190420154240.GA3135@ednor.casa.cgf.cx> In-Reply-To: <20190420154240.GA3135@ednor.casa.cgf.cx> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SW-Source: 2019-q2/txt/msg00010.txt.bz2 Hi, Thank all of you for helping. Turned out my private keys were messed up. = It's all fixed now. Sorry for disturbing. Thanks, bin From: Christopher Faylor Sent: 20 April 2019 23:42 To: ben narwal Cc: overseers@gcc.gnu.org Subject: Re: Question about write-access svn repository of my account =A0 On Sat, Apr 20, 2019 at 10:11:47AM +0000, ben narwal wrote: >I have an account on sourceware.org/gcc.gnu.org which is >"amker@gcc.gnu.org".=A0 I also had write access previously with below >public key registered: > >ssh-rsa >AAAAB3NzaC1yc2EAAAABIwAAAQEApQ5PKbKVjUpIL/I4CAckNthGXmayvAKz5TXQbDm529FoxO= mnDrejRW+0ttQ7KAUU9fXSrRhMpweO2SiP9xqYXlP5tgfFKG8I9oqCLgTKRAa6pk1APZBTQteeI= ywbyJTVCTimeznYwPqrEbf340ppeQB/PFGeP434HjLT+QQqIEeT8V60FdVSL6H3p5of924nofn+= eLh8JT/j/cpykDqLHzxb9yabK4nRdUlNihZp2Tu6ziax39awM8XkP1qPXwHMlT3l25yZ6yl14UR= Pa/WBWWGlq3N/FCcSg6cMjMNb814Y2YQVxT2IBxt+wgaEzGfTfyKJUp6RAoAgSsRmRqLaKw=3D= =3D binche01@binche01-desktop > >Recently I ran into problem in accessing write-access svn repository >while read-only access is fine with below command line: svn checkout >svn://gcc.gnu.org/svn/gcc/trunk SomeLocalDir > >Also I didn't made any change to either svn or ssh configuration, so >could you help me check if the public key is still registered correctly >to my account please?=A0 Thanks very much for your time. "ran into a problem" doesn't give us much to go on. What was the actual error? Does "ssh sourceware.org alive" work for you?