From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 2F1D63858C60 for ; Fri, 21 Jan 2022 10:40:08 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2F1D63858C60 Received: from tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 32D5030002C2; Fri, 21 Jan 2022 11:40:04 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id AE8AA4000836; Fri, 21 Jan 2022 11:40:03 +0100 (CET) Message-ID: <1ec15cd41df0ee68c8cac108a3e7c009385291d7.camel@klomp.org> Subject: Re: Can't push the commit in binutils-gdb From: Mark Wielaard To: =?UTF-8?Q?=E5=A4=8F=E7=AB=8B=E6=96=B9?= , Overseers mailing list Date: Fri, 21 Jan 2022 11:40:03 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, BODY_8BITS, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2022 10:40:10 -0000 Hi, On Fri, 2022-01-21 at 16:39 +0800, =E5=A4=8F=E7=AB=8B=E6=96=B9 via Overseer= s wrote: > I meet a problem while pushing the commit into binutild-gdb, I got an > error: > "fatal: remote error: service not enabled: /git/binutils-gdb.git" >=20 > As a maintainer of binutils-gdb for C-SKY, I have upload a public key > previously. Could you help to check that? >=20 >=20 > Here is my public key: > "ssh-rsa > AAAAB3NzaC1yc2EAAAADAQABAAAAgQCrECRu7/Z+tyjK/VJnc1gMNvZxNqnuDqpWjpZax > ErDOstradjiKXFykQp6Ps+VWDYei3RENSVKu8iS+JLzRMuHc6plG1UcfHOdV7FaEugiEs > GnCxXDK4Z9cFo3vNQKF1YmiiD19pMmTH8XmLFhjAGZi244PvR4AHi7XQ7d1RXchw=3D=3D= =20 > xlf194833@PF1K7H4W" Yes, there is an user with that key. Are you sure you are pushing through ssh? The above message looks like you are pushing through http. Cheers, Mark