From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: git clone https failed on 2.31.1-2, works on 2.31.1-1
Date: Wed, 9 Jun 2021 19:37:54 +0200 [thread overview]
Message-ID: <0c9ed830-25e0-f701-92a0-4105a4a6bd42@gmail.com> (raw)
In-Reply-To: <07c301d75d54$051b24e0$0f516ea0$@pdinc.us>
On 09.06.2021 19:22, Jason Pyeron wrote:
> Just did a fresh cygwin install base + git+nano+wget
>
> Clone is not happy.
>
> Is this an issue of: ooks like not having (lib)curl-devel installed when you compile git ( https://stackoverflow.com/a/13018777/58794 )
>
> USERNAME@HOSTNAME1 /projects
> $ git clone https://HOSTNAME2/URL.git -b files-stsw-link009.zip
> Cloning into 'sharptown-files-stlink'...
> fatal: unable to find remote helper for 'https'
>
It works for me
$ cygcheck -c git
Cygwin Package Information
Package Version Status
git 2.31.1-2 OK
$ git clone https://github.com/nco/nco.git
Cloning into 'nco'...
remote: Enumerating objects: 108577, done.
remote: Counting objects: 100% (1195/1195), done.
remote: Compressing objects: 100% (499/499), done.
remote: Total 108577 (delta 904), reused 956 (delta 677), pack-reused 107382
Receiving objects: 100% (108577/108577), 63.37 MiB | 8.94 MiB/s, done.
Resolving deltas: 100% (89814/89814), done.
and curl was present during the build
$ cygcheck /usr/libexec/git-core/git-http-fetch.exe
D:\cygwin64\usr\libexec\git-core\git-http-fetch.exe
D:\cygwin64\bin\cygcurl-4.dll
..
$ cygcheck /usr/libexec/git-core/git-http-push.exe
D:\cygwin64\usr\libexec\git-core\git-http-push.exe
D:\cygwin64\bin\cygcurl-4.dll
...
may be you had an incomplete installation ?
Marco
next prev parent reply other threads:[~2021-06-09 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 17:22 Jason Pyeron
2021-06-09 17:37 ` Marco Atzeri [this message]
2021-06-09 17:54 ` [cygwin] " Jason Pyeron
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=0c9ed830-25e0-f701-92a0-4105a4a6bd42@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).