Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Error fetching from sf over ssh
- X-seq: zsh-workers 49734
- From: "Daniel Shahaf" <d.s@xxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: Error fetching from sf over ssh
- Date: Tue, 01 Feb 2022 07:33:57 +0000
- Archived-at: <https://zsh.org/workers/49734>
- In-reply-to: <CAH+w=7aH3PzUUxqy8eLxvYtHMn+ibW+QnaeD03YF-wVvhR8cAQ@mail.gmail.com>
- List-id: <zsh-workers.zsh.org>
- References: <YfizcnytTiEHjZCI@CptOrmolo.darkstar> <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@xxxxxxxxx> 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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author