public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Daisuke Fujimura <booleanlabel@gmail.com>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] ruby-mini_portile2 2.8.2
Date: Thu, 8 Jun 2023 14:37:20 +0100	[thread overview]
Message-ID: <528f1c30-395c-dac2-650f-9811179d2b00@dronecode.org.uk> (raw)
In-Reply-To: <CAA3frXSMV8pP8n3KnE7X7dsPh=+sZGf8_gt1LMNziiS7wgakfQ@mail.gmail.com>

On 08/06/2023 14:27, Daisuke Fujimura via Cygwin-apps wrote:
> Thank you for your response.
> It seems that the repository has not been set up yet.
> Could you please check?

It seems like the package name was typoed ('ruby-mini-portile' rather 
than 'ruby-mini-portile2').

That should be fixed now.

> ```
> $ git remote -v
> origin ssh://cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org/git/cygwin-packages/ruby-mini_portile2.git
> (fetch)
> origin ssh://cygwin-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org/git/cygwin-packages/ruby-mini_portile2.git (push)
> $ git push origin master
> 
> FATAL -- ACCESS DENIED
> Repo            git/cygwin-packages/ruby-mini_portile2
> User            Daisuke_Fujimura
> Stage           Before git was called
> Operation       Repo write
> 
> FATAL: W any git/cygwin-packages/ruby-mini_portile2 Daisuke_Fujimura
> DENIED by fallthru
> (or you mis-spelled the reponame)
> fatal: Could not read from remote repository.
> 
> Please make sure you have the correct access rights
> and the repository exists.
> ```
> 

  reply	other threads:[~2023-06-08 13:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 13:25 Daisuke Fujimura
2023-06-07  5:04 ` Marco Atzeri
2023-06-08 13:27   ` Daisuke Fujimura
2023-06-08 13:37     ` Jon Turney [this message]
2023-06-10  4:58       ` Daisuke Fujimura
2023-06-10  6:13         ` Marco Atzeri

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=528f1c30-395c-dac2-650f-9811179d2b00@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).