Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Andreas Schroeck
    @schroeca
    I have some issues with my msys2 installation. I can not update the git-for-windows repository. I have tried a lot of different things with the keyring, because it looks like an issue with the key
    Is this a known issue? I could not find any help on google
    image.png
    Johannes Schindelin
    @dscho
    pacman-key --lsign-key E8325679DFFF09668AD8D7B67115A57376871B1C
    (see https://github.com/git-for-windows/git/wiki/Install-inside-MSYS2-proper#the-steps)
    1 reply
    Stephen Lyons
    @SlySven
    Anyone know who owns the gpg key: 91883E11E83DC29D14104DB4EDD44359093056EE - I am having the same sort of problem as @schroeca but for this key instead:
    stephen@Rachel MSYS ~
$ pacman -Syuu
error: git-for-windows-mingw64: key "91883E11E83DC29D14104DB4EDD44359093056EE" is unknown
:: Import PGP key 91883E11E83DC29D14104DB4EDD44359093056EE? [Y/n] y
error: key "91883E11E83DC29D14104DB4EDD44359093056EE" could not be looked up remotely
error: git-for-windows-mingw32: key "91883E11E83DC29D14104DB4EDD44359093056EE" is unknown
:: Import PGP key 91883E11E83DC29D14104DB4EDD44359093056EE? [Y/n] y
error: key "91883E11E83DC29D14104DB4EDD44359093056EE" could not be looked up remotely
:: Synchronizing package databases...
 git-for-windows-mingw64                                   15.7 KiB  10.7 KiB/s 00:01 [################################################] 100%
 git-for-windows-mingw32                                   15.7 KiB  31.4 KiB/s 00:01 [################################################] 100%
 mingw32 is up to date
 mingw64 is up to date
 ucrt64 is up to date
 clang64 is up to date
 msys is up to date
error: git-for-windows-mingw64: key "91883E11E83DC29D14104DB4EDD44359093056EE" is unknown
:: Import PGP key 91883E11E83DC29D14104DB4EDD44359093056EE? [Y/n] n
error: git-for-windows-mingw32: key "91883E11E83DC29D14104DB4EDD44359093056EE" is unknown
:: Import PGP key 91883E11E83DC29D14104DB4EDD44359093056EE? [Y/n] n
error: failed to synchronize all databases (invalid or corrupted database (PGP signature))

stephen@Rachel MSYS ~
    Johannes Schindelin
    @dscho
    It's my GPG key. It's the same as @schroeca reported.
    Stephen Lyons
    @SlySven
    But that is a different one, isn't it:
    91883E11E83DC29D14104DB4EDD44359093056EE
    verses:
    E8325679DFFF09668AD8D7B67115A57376871B1C
    Johannes Schindelin
    @dscho
    The former is a subkey of the latter.
    Have you tried following the steps in the linked wiki page?
    Stephen Lyons
    @SlySven
    Ah, one is your signing key and the other your authentication one?
    Johannes Schindelin
    @dscho
    s/authentication/primary/
    Stephen Lyons
    @SlySven
    :stuck_out_tongue_closed_eyes:
    David Macek
    @elieux
    $ gpg --homedir /etc/pacman.d/gnupg/ --with-subkey-fingerprints --list-keys 0x91883E11E83DC29D14104DB4EDD44359093056EE
gpg: Note: trustdb not writable
pub   rsa4096 2021-03-23 [SC] [expires: 2026-03-22]
      E8325679DFFF09668AD8D7B67115A57376871B1C
uid           [ultimate] Johannes Schindelin <johannes.schindelin@gmx.de>
sub   rsa4096 2021-03-23 [E] [expires: 2026-03-22]
      958D57D8AD8823F11D033AAB6D0EA17128B145BC
sub   rsa4096 2021-03-23 [S] [expires: 2026-03-22]
      91883E11E83DC29D14104DB4EDD44359093056EE
    Stephen Lyons
    @SlySven
    AH, RTFM - the wiki step 2 was enough to get things going again...!
    David Macek
    @elieux
    Took me a while to find the right syntax. :D
    Stephen Lyons
    @SlySven
    curl -L https://raw.githubusercontent.com/git-for-windows/build-extra/HEAD/git-for-windows-keyring/git-for-windows.gpg |
pacman-key --add - &&
pacman-key --lsign-key E8325679DFFF09668AD8D7B67115A57376871B1C &&
pacman-key --lsign-key 3B6D86A1BA7701CD0F23AED888138B9E1A9F3986
    :thinking: Would it be worthwhile publishing that public key to https://keys.openpgp.org ?
    Johannes Schindelin
    @dscho
    It's already there: https://keys.openpgp.org/vks/v1/by-fingerprint/E8325679DFFF09668AD8D7B67115A57376871B1C
    David Macek
    @elieux
    I did look for it there, but somehow missed it.
    Johannes Schindelin
    @dscho
    No, you didn't.
    David Macek
    @elieux
    I guess I expected a printout instead of just a link.
    Johannes Schindelin
    @dscho
    5 minutes ago it wasn't there :-)
    Was that your Yubikey?
    ;-)
    David Macek
    @elieux
    :D Okay, you got me.
    Stephen Lyons
    @SlySven

    5 minutes ago it wasn't there :-)

    Yes, it wasn't...

    *sigh*

    Stephen Lyons
    @SlySven
    Ah, it has been a while and the update to my setup needs a 3GB download - and I'm currently on a public WiFI - really need to wait 'til I get home and back on a fat pipe to the Interweb...
    David Macek
    @elieux
    Do we know @okrc?
    Johannes Schindelin
    @dscho
    I don't.
    David Macek
    @elieux
    I'm just wondering about https://github.com/git-for-windows/git/wiki/Install-inside-MSYS2-proper/_history.
    The package name was switched from git-credential-manager to git-credential-manager-core and then back.
    ... by the same person.
    Would that correlate with an actual development in this area?
    Johannes Schindelin
    @dscho
    Yes ;-)
    The mingw-w64-git-credential-manager package originally contained Git Credential Manager for Windows.
    That project is implemented in C# using .NET.
    There was also the Git Credential Manger for Linux and MacOSX, implemented in Java, but it fell unmaintained years ago.
    Then an effort was started to extend Git Credential Manager for Windows to cover also Linux and MacOSX (which by then had been renamed to macOS).
    Naturally, this meant to adjust the C# code to be able to use .NET Core in addition to .NET Framework.
    It's quite confusing, I find, that there is a .NET Core vs .NET Framework distinction. The tl;dr is that Core is platform-independent, while Framework is Windows-only.
    That effort was started as a fork, Git Credential Manager Core.
    Johannes Schindelin
    @dscho
    (A fork, because it was an experiment, a proof-of-concept if you want, without being certain that it works as intended.)
    As GCM Core was developed, GCM for Windows stalled a bit, and eventually fell unmaintained.
    That's when I started bundling the former as mingw-w64-git-credential-manager-core, side-by-side with GCM for Windows.
    We eventually deprecated the latter, and finally dropped it.
    Then the Git Credential Manager Core project was renamed to Git Credential Manager and moved to its own org (it lived in https://github.com/microsoft/ before, now lives in https://github.com/GitCredentialManager).
    And that's when I renamed mingw-w64-git-credential-manager-core to mingw-w64-git-credential-manager.
    David Macek
    @elieux
    Makes sense. Thanks for the explanation.
    Christian Fiderer
    @cfiderer

    Hi all,
    I'm struggling with git bash: I try to exec into the shell of a kubernetes container, but git bash always prepends a windows path (kubectl run test --image=alpine:latest -it /bin/sh gets executed as "C:\Program Files\Docker\Docker\resources\bin\kubectl.exe" run test --image=alpine:latest -it "C:/Program Files/Git/usr/bin/sh".

    How can I prevent the expansion of the /bin/sh part? Quoting with single quotes or double quotes didn't help...

    David Macek
    @elieux
    Hi. Try kubectl run test --image=alpine:latest -it //bin/sh.