public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Git not fetching https repository: cannot open shared object file (probably cyggsasl-18.dll ?)
Date: Mon, 31 Oct 2022 11:44:52 +0000	[thread overview]
Message-ID: <20221031114452.kzfge5hdat4ov5de@lucy.dinwoodie.org> (raw)
In-Reply-To: <Y1+wqQKHqV6A4bRQ@nuvolo>

On Mon, Oct 31, 2022 at 12:25:29PM +0100, Arrigo Marchiori via Cygwin wrote:
> Dear All,
> 
> on my Cygwin installation, updated today, I cannot run `git fetch'
> on a https repository.
> 
> Transcript:
> 
> ----8<--------8<--------8<--------8<--------8<--------8<--------8<---------
> 
> $ git fetch
> C:/cygwin64/usr/libexec/git-core/git-remote-https.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
> 
> $ cygcheck.exe /cygdrive/c/cygwin64/usr/libexec/git-core/git-remote-https.exe
> c:\cygwin64\usr\libexec\git-core\git-remote-https.exe
>   C:\cygwin64\bin\cygcurl-4.dll
>     C:\cygwin64\bin\cygbrotlidec-1.dll
>       C:\cygwin64\bin\cygwin1.dll
>         C:\Windows\system32\KERNEL32.dll
>           C:\Windows\system32\ntdll.dll
>           C:\Windows\system32\KERNELBASE.dll
>       C:\cygwin64\bin\cygbrotlicommon-1.dll
>     C:\cygwin64\bin\cygcrypto-1.1.dll
>       C:\cygwin64\bin\cygz.dll
>     C:\cygwin64\bin\cyggssapi_krb5-2.dll
>       C:\cygwin64\bin\cygk5crypto-3.dll
>         C:\cygwin64\bin\cygkrb5support-0.dll
>           C:\cygwin64\bin\cygintl-8.dll
>             C:\cygwin64\bin\cygiconv-2.dll
>       C:\cygwin64\bin\cygkrb5-3.dll
>         C:\cygwin64\bin\cygcom_err-2.dll
>           C:\cygwin64\bin\cyggcc_s-seh-1.dll
>     C:\cygwin64\bin\cygidn2-0.dll
>     C:\cygwin64\bin\cyglber-2.dll
>     C:\cygwin64\bin\cygldap-2.dll
>       C:\cygwin64\bin\cygsasl2-3.dll
>       C:\cygwin64\bin\cygssl-1.1.dll
>     C:\cygwin64\bin\cygnghttp2-14.dll
>     C:\cygwin64\bin\cygpsl-5.dll
>       C:\cygwin64\bin\cygunistring-2.dll
>     C:\cygwin64\bin\cygssh2-1.dll
>     C:\cygwin64\bin\cygzstd-1.dll
>   C:\cygwin64\bin\cygpcre2-8-0.dll
> cygcheck: track_down: could not find cyggsasl-18.dll
> 
> ----8<--------8<--------8<--------8<--------8<--------8<--------8<---------
> 
> I cannot find any packages providing that cyggsasl-18.dll

This is working fine for me, but you're definitely not the only person
reporting problems involving cyggsasl-18.dll, per
https://cygwin.com/pipermail/cygwin/2022-October/252386.html

Notably, it's working fine for me, and my local packages are up to date
with my normal mirror, but my mirror is still serving curl 7.85.0-1 as
current.  That suggests a temporary workaround might be to install
7.85.0-1 (or earlier) of any curl packages you have installed.

> Please let me know if you need any more information.

If the above doesn't help, the standard diagnostics described at the
problem reporting page, particularly the requested cygcheck output,
would be useful:

> Problem reports:      https://cygwin.com/problems.html

  reply	other threads:[~2022-10-31 11:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Y1+wqQKHqV6A4bRQ.ref@nuvolo>
2022-10-31 11:25 ` Arrigo Marchiori
2022-10-31 11:44   ` Adam Dinwoodie [this message]
2022-10-31 11:58     ` Arrigo Marchiori

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=20221031114452.kzfge5hdat4ov5de@lucy.dinwoodie.org \
    --to=adam@dinwoodie.org \
    --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).