Git: install inside MSYS2: signature from "Johannes Schindelin <...>" is unknown trust
Setup
- Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
$ cmd.exe /c ver
** Microsoft Windows [Version 10.0.15063] **
Details
I am following this installation guide:
On a fresh install of msys2, I did an update using pacman -Syuu ang got no error.
Then I added the following in pacman.conf before section [mingw32]:
[git-for-windows]
SigLevel = Optional TrustedOnly
Server = https://dl.bintray.com/git-for-windows/pacman/$arch
when I run pacman -Sy I get the following output
:: Synchronizing package databases...
git-for-windows 7.6 KiB 7.42M/s 00:00 [#####################] 100%
git-for-windows.sig 543.0 B 0.00B/s 00:00 [#####################] 100%
error: git-for-windows: key "BB3AA74136C569BB" is unknown
:: Import PGP key 4096R/3B6D86A1BA7701CD0F23AED888138B9E1A9F3986, "Johannes Schindelin <[email protected]>", created: 2013-09-13? [Y/n] Y
error: git-for-windows: signature from "Johannes Schindelin <[email protected]>" is unknown trust
error: failed to update git-for-windows (invalid or corrupted database (PGP signature))
mingw32 is up to date
mingw64 is up to date
msys is up to date
error: database 'git-for-windows' is not valid (invalid or corrupted database (PGP signature))
I tried the following with no luck:
pacman-key --init
pacman-key --populate msys2
pacman-key --refresh-keys
Is there something wrong?
klarezz
All 13 comments
Yes, there is something wrong.
The required keyring is in git-for-windows-keyring (which you can download manually here: https://bintray.com/git-for-windows/pacman/git-for-windows-keyring), and that package is a dependency of git-extra, which is installed implicitly in Git for Windows' SDK.
You probably set up a custom system based on MSYS2 but not using Git for Windows' SDK, and you simply missed that git-extra has to be installed (and re-installed after certain packages are upgraded, such as filesystem and pacman).
dscho
on 15 Jul 2017
Thank you for the answer, I am new to pacman. It worked after running the following script:
wget https://raw.githubusercontent.com/git-for-windows/build-extra/master/git-for-windows-keyring/git-for-windows.gpg
pacman-key --add ./git-for-windows.gpg
pacman-key --list-keys
pacman-key --lsign-key 1A9F3986
rm ./git-for-windows.gpg
Side question (probably related to pacman) : is it the expected behavior for the install not to use symbolic links (binaries are duplicated in git-core) despite them bieng enabled (export MSYS=winsymlinks:nativestrict) and working correctly using ln -s command?
klarezz
on 19 Jul 2017
wget https://raw.githubusercontent.com/git-for-windows/build-extra/master/git-for-windows-keyring/git-for-windows.gpg pacman-key --add ./git-for-windows.gpg pacman-key --list-keys pacman-key --lsign-key 1A9F3986 rm ./git-for-windows.gpg
That's a good find!
I think the following also works (and avoids a temporary file):
curl -L https://raw.githubusercontent.com/git-for-windows/build-extra/master/git-for-windows-keyring/git-for-windows.gpg |
pacman-key --add - &&
pacman-key --lsign-key 1A9F3986
Side question (probably related to pacman) : is it the expected behavior for the install not to use symbolic links (binaries are duplicated in git-core) despite them bieng enabled (export MSYS=winsymlinks:nativestrict) and working correctly using ln -s command?
The MSYS environment variable is an environment variable, hence possibly transient. As such, yes, I think this is expected. It is an inherited feature of MSYS2, though, so I am not quite certain that my interpretation is correct.
dscho
on 19 Jul 2017
This problem is still happening when following this guide - https://github.com/git-for-windows/git/wiki/Install-inside-MSYS2-proper
I solved it by using the command from above:
curl -L https://raw.githubusercontent.com/git-for-windows/build-extra/master/git-for-windows-keyring/git-for-windows.gpg | pacman-key --add - && pacman-key --lsign-key 1A9F3986
I also had issues during fetching and pulling, like:
/d/dev/lib/Catch
$ git fetch --all
Fetching origin
fatal: unable to access 'https://github.com/philsquared/Catch.git/': error setting certificate verify locations:
CAfile: D:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
CApath: none
error: Could not fetch origin
I guess it was because of a remaning configuration from previous Git for Windows installation.
I solved it with:
git config --system http.sslcainfo /mingw64/ssl/certs/ca-bundle.crt
ArekPiekarz
on 3 Oct 2017
I updated the wikipage and added this step.
elieux
on 3 Oct 2017
I updated the wikipage and added this step.
Please note that it is the responsibility of git-extra's post-install script to initialize Git's system config: https://github.com/git-for-windows/build-extra/blob/c7f09a1088eb455dd9d6db196fddc0c9119efdcc/git-extra/git-extra.install#L21-L22
dscho
on 4 Oct 2017
The guide doesn't mention git-extra, so it would be a good move to add it there.
ArekPiekarz
on 4 Oct 2017
it would be a good move to add it there.
It would also be good to help the project by lessening the load on the maintainer.
dscho
on 5 Oct 2017
Understood ;-). I will try to prepare a pull request.
ArekPiekarz
on 7 Oct 2017
It turns out a pull request is not required to edit the wiki. I added git-extra and also changed commands to use pacboy instead of pacman - no more need to write mingw-w64-x86_64- before every 64-bit package and the parameters are easier to understand and remember.
ArekPiekarz
on 9 Oct 2017
----- Original Message -----
From: Arkadiusz Piekarz
To: git-for-windows/git
Cc: Subscribed
Sent: Monday, October 09, 2017 8:35 PM
Subject: Re: [git-for-windows/git] install inside MSYS2: signature from "Johannes Schindelin <...>" is unknown trust (#1238)
It turns out a pull request is not required to edit the wiki. I added git-extra and also changed commands to use pacboy instead of pacman - no more need to write mingw-w64-x86_64- before every package and the parameters are easier to understand and remember.
What is 'pacboy' - Is there a bigger reference for this?
--
Philip
PhilipOakley
on 9 Oct 2017
It's installed by default in Msys2. It was designed to wrap pacman commands into short human readable form and also to ease working with 32/64-bit package names and different repositories.
It originated here: https://github.com/renatosilva/pactoys
Quoting its help:
Pacboy 2016.6.24 Copyright (C) 2015, 2016 Renato Silva Licensed under BSD This is a pacman wrapper for MSYS2 which handles the package prefixes automatically, and provides human-friendly commands for common tasks. Usage: pacboy [command] [arguments] Arguments will be passed to pacman or pkgfile after translation: For 64-bit MSYS2, name:i means i686-only For 64-bit MSYS2, name:x means x86_64-only For MSYS shell, name:m means mingw-w64 For all shells, name: disables any translation for name For all shells, repository::name means repository/name Commands: sync Shorthand for --sync or --upgrade update Shorthand for --sync --refresh --sysupgrade refresh Shorthand for --sync --refresh find Shorthand for --sync --search packages Shorthand for --sync --list files Shorthand for --query --list [--file] info Shorthand for --query --info [--file] origin Shorthand for --query --owns or pkgfile remove Shorthand for --remove --recursive debug Verbose output for the above commands
ArekPiekarz
on 9 Oct 2017
It seems that pacboy is indeed installed in Git for Windows' SDK by default: https://github.com/git-for-windows/git-sdk-64/blob/master/usr/bin/pacboy
dscho
on 12 Oct 2017
Related issues
tldzyx
路
3Comments
dscho
路
3Comments
Unknow0059
路
3Comments
michaelblyons
路
5Comments
jesterKing
路
3Comments
Most helpful comment
That's a good find!
I think the following also works (and avoids a temporary file):
The
MSYSenvironment variable is an environment variable, hence possibly transient. As such, yes, I think this is expected. It is an inherited feature of MSYS2, though, so I am not quite certain that my interpretation is correct.