public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin-apps@cygwin.com
Subject: Re: Unable to 'git push' to /git/cygwin-packages/*
Date: Fri, 15 Mar 2024 02:00:28 -0700	[thread overview]
Message-ID: <df3897ac-26c9-4307-9c5c-343ea83823bf@maxrnd.com> (raw)
In-Reply-To: <72a7a008-6e77-47c0-a3fa-eb72827c18ca@dronecode.org.uk>

On 3/14/2024 9:07 AM, Jon Turney via Cygwin-apps wrote:
> On 14/03/2024 15:39, Mark Geisert via Cygwin-apps wrote:
>> On 3/14/2024 2:42 AM, Jon Turney via Cygwin-apps wrote:
>>> On 14/03/2024 05:45, Mark Geisert via Cygwin-apps wrote:
>>>> Hi folks,
>>>> I'm getting the error:
>>>>
>>>> fatal: remote error: service not enabled: /git/cygwin-packages/sshfs
>>>>
>>>> when I attempt 'git push' to that repository.  The same happens with 
>>>> all the repositories for my packages.  It's been this way for a 
>>>> couple days at least.
>>>>
>>>> Have I forgotten some step in the connection at my end?  I'm running 
>>>> ssh-agent.
>>>
[...]
>>> What is the repository URL you are trying to push to (git remote -v)?
>>
>> /usr/src/upstaging/sshfs git remote -v
>> origin     git://cygwin.com/git/cygwin-packages/sshfs (fetch)
>> origin     git://cygwin.com/git/cygwin-packages/sshfs (push)
> 
> This maybe looks like pilot error.
> 
> We don't allow pushing using the git:// protocol (since this protocol 
> doesn't do any authorization, pushes with a it are very rarely enabled)
> 
> 
> I suggest you need to do
> 
>    git push 
> ssh://cygwin@cygwin.com:git/cygwin-packages/sshfs
> 
> to push successfully.
> 
> If that works, I suggest you memorialize that by doing
> 
>    git remote set-url origin --push 
> ssh://cygwin@cygwin.com:git/cygwin-packages/sshfs
> 
> which will cause git to automatically use the ssh URL with a simple 'git 
> push'.

With a minor correction ("/git" instead of "git" in the URL) this works 
fine.  I've made the git config change for all my projects.

> You might like to review the last time we discussed this at [1]
> 
> (Note that's slightly different, as to push to cygwin-apps repositories 
> you must present the key as 
> yourusername-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org, whereas for 
> cygwin-packages repositories, you can present the key as 
> cygwin-rDBXBDvO6BWXj1p+fO2waQ@public.gmane.org There are just different 
> due to historical reasons.)
> 
> [1] https://cygwin.com/pipermail/cygwin-apps/2021-September/041539.html

Thanks very much, Jon.

..mark


  parent reply	other threads:[~2024-03-15  9:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  5:45 Mark Geisert
2024-03-14  9:42 ` Jon Turney
2024-03-14 15:39   ` Mark Geisert
2024-03-14 16:07     ` Jon Turney
2024-03-14 18:26       ` Corinna Vinschen
2024-03-15  9:02         ` Mark Geisert
2024-03-15  9:00       ` Mark Geisert [this message]
2024-03-15 13:16         ` Jon Turney

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=df3897ac-26c9-4307-9c5c-343ea83823bf@maxrnd.com \
    --to=mark@maxrnd.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).