From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 4/4] azure: Switch to use the MSYS2 official installer as the CI base
Date: Tue, 28 Jul 2020 11:53:50 -0400 [thread overview]
Message-ID: <20200728155350.GS6965@bill-the-cat> (raw)
In-Reply-To: <1595927204-27088-4-git-send-email-bmeng.cn@gmail.com>
On Tue, Jul 28, 2020 at 02:06:44AM -0700, Bin Meng wrote:
> 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>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200728/710b1724/attachment.sig>
next prev parent reply other threads:[~2020-07-28 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 9:06 [PATCH 1/4] azure: Use a login shell everywhere for MSYS2 build Bin Meng
2020-07-28 9:06 ` [PATCH 2/4] azure: Drop 32-bit " Bin Meng
2020-07-28 15:53 ` Tom Rini
2020-07-28 9:06 ` [PATCH 3/4] azure: Add the missing build dependency for " Bin Meng
2020-07-28 15:53 ` Tom Rini
2020-07-28 9:06 ` [PATCH 4/4] azure: Switch to use the MSYS2 official installer as the CI base Bin Meng
2020-07-28 15:53 ` Tom Rini [this message]
2020-07-28 15:53 ` [PATCH 1/4] azure: Use a login shell everywhere for MSYS2 build Tom Rini
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=20200728155350.GS6965@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.