zsh-workers
 help / color / mirror / code / Atom feed
From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: Error fetching from sf over ssh
Date: Tue, 01 Feb 2022 07:33:57 +0000	[thread overview]
Message-ID: <52331156-1996-47da-a0b9-16e77bac8cc9@www.fastmail.com> (raw)
In-Reply-To: <CAH+w=7aH3PzUUxqy8eLxvYtHMn+ibW+QnaeD03YF-wVvhR8cAQ@mail.gmail.com>

Bart Schaefer wrote on Tue, 01 Feb 2022 05:26 +00:00:
> On Mon, Jan 31, 2022 at 8:14 PM Matthew Martin <phy1729@gmail.com> wrote:
>
>> When attempting to fetch from sourceforge over ssh, the attempt fails
>>
>
> Something's gone amiss at sourceforge, my SSH keys don't work any longer
> and I get prompted for a password when trying to do git ops.
>
> I can still fetch or clone with git://git.code.sf.net/p/zsh/code but i
> can't push.  I even created a new key and added it to my SSH profile, but
> it doesn't work.

«ssh shell.sourceforge.net create» prompts for a password too.  I didn't
attempt to provide one as I assumed that'd lead to treating me as
a password guesser.

I assume SF will be back in a few hours.

If not… we'll just put a master repository somewhere else.  We have at
least zsh.org, gitlab, and github as options.  I don't think there's anything
else tying us to sourceforge, other than the Web site, and we were going
to move that to zsh.org anyway.  

I've also grabbed a copy of the settings in the sourceforge "Admin"
screens, including the list of people with push access, and queued
an "Export".

According to sourceforge's emailed push notifications, the last push was
Mikael's 8bf0f0, log message "49694 + doc".  I pulled a copy of that, so
now at least four of us have copies of the whole history.  github and
gitlab have both mirrored that commit, too.


  reply	other threads:[~2022-02-01  7:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01  4:13 Matthew Martin
2022-02-01  5:26 ` Bart Schaefer
2022-02-01  7:33   ` Daniel Shahaf [this message]
2022-02-01  7:43     ` Daniel Shahaf
2022-02-01 18:31     ` Bart Schaefer
2022-02-01 21:03       ` Bart Schaefer

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=52331156-1996-47da-a0b9-16e77bac8cc9@www.fastmail.com \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).