From: Jon Turney <jon.turney@dronecode.org.uk>
To: Daisuke Fujimura <booleanlabel@gmail.com>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITA] rubygems 3.4.12
Date: Mon, 17 Apr 2023 11:40:16 +0100 [thread overview]
Message-ID: <bb57b016-9747-4b96-cf9a-feb5849c69c9@dronecode.org.uk> (raw)
In-Reply-To: <CAA3frXRPNfO3qzGzdsG=cvTR3jA_xiG9JfGZ4MpjUkP87x38hA@mail.gmail.com>
On 17/04/2023 11:28, Daisuke Fujimura via Cygwin-apps wrote:
>> I changed maintainer-ship to you
>
> I can't push on git, is there anything else I should do?
>
> I confirmed that my name is mentioned in the rubygems section of
> cygwin-pkg-maint.
>
> ```
> $ git remote -v
> origin ssh://cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org/git/cygwin-packages/rubygems.git (fetch)
> origin ssh://cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org/git/cygwin-packages/rubygems.git (push)
>
> $ git push origin master
> kex_exchange_identification: Connection closed by remote host
> Connection closed by 8.43.85.97 port 22
This just looks like problem establishing the ssh connection.
If it's not a transient problem, you can try 'ssh cygwin@cygwin.com
alive', and then maybe adding '-vvv' may give some hints as to what's
going wrong...
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> ```
next prev parent reply other threads:[~2023-04-17 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 12:55 Daisuke Fujimura
2023-04-15 17:40 ` Marco Atzeri
2023-04-15 18:20 ` Jon Turney
2023-04-16 1:30 ` Daisuke Fujimura
2023-04-17 10:28 ` Daisuke Fujimura
2023-04-17 10:40 ` Jon Turney [this message]
2023-04-17 11:29 ` Daisuke Fujimura
2023-04-17 16:22 ` Brian Inglis
2023-04-17 22:48 ` Daisuke Fujimura
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=bb57b016-9747-4b96-cf9a-feb5849c69c9@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=booleanlabel@gmail.com \
--cc=cygwin-apps@cygwin.com \
/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).