diff options
| author | Bin Meng <bmeng.cn@gmail.com> | 2020-07-28 02:06:44 -0700 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2020-07-28 08:42:20 -0400 |
| commit | 437e70f7c32d66902bedaeb24fda819b6495f660 (patch) | |
| tree | 7975ac37814963c5ac73f1ee0f3ec473dd8d0f13 /configs/imx28_xea_defconfig | |
| parent | d126e3cdb740cd7d8717477e09f7a016030e1805 (diff) | |
azure: Switch to use the MSYS2 official installer as the CI base
Recent CI failures were seen [1] when building MSYS2 Windows host
tools. The error messages are something like:
downloading mingw32.db...
downloading mingw32.db.sig...
error: mingw32: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: mingw32: signature from "David Macek <david.macek.0@gmail.com>" is unknown trust
error: failed to update mingw32 (invalid or corrupted database (PGP signature))
Per the MSYS2 official news [2], this was caused by a packager
switch and several solutions were suggested, e.g.: a new package
of msys2-keyring and a new msys2 installer that includes them are
released. However right now we have been using the MSYS2 github
CI base repo [3] for the MSYS2 build in U-Boot, but per the project
information on the github webpage, it says: "This repository is
unused/deprecated and will be remove after 2021-01-01". Since it is
unmaintained it's unlikely the new PGP keys will be included in the
git repo, and the only choice is to switch to use the MSYS2 official
installer as the CI base instead.
[1] https://dev.azure.com/u-boot/u-boot/_build/results?buildId=975
[2] https://www.msys2.org/news/#2020-06-29-new-packagers
[3] https://github.com/msys2/msys2-ci-base
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Diffstat (limited to 'configs/imx28_xea_defconfig')
0 files changed, 0 insertions, 0 deletions