From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: David Lechner <david@lechnology.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/lego_ev3: update to U-Boot 2021.07
Date: Sun, 17 Oct 2021 10:15:23 +0200 [thread overview]
Message-ID: <20211017081523.GE2400@scaer> (raw)
In-Reply-To: <20211016213626.3264701-1-david@lechnology.com>
David, All,
On 2021-10-16 16:36 -0500, David Lechner spake thusly:
> Buildroot CI has been failing due to 404 error on older U-Boot.
The real problem is that the certificate presented by the https server
at ftp.denx.de, can't be validated:
wget --passive-ftp -nd -t 3 -O '/builds/buildroot.org/buildroot/output/build/.u-boot-2018.11.tar.bz2.rycJD2/output' 'https://ftp.denx.de/pub/u-boot/u-boot-2018.11.tar.bz2'
--2021-10-14 13:07:22-- https://ftp.denx.de/pub/u-boot/u-boot-2018.11.tar.bz2
Resolving ftp.denx.de (ftp.denx.de)... 85.214.49.3, 2a01:238:43f4:4600:bc64:4f44:381f:1163
Connecting to ftp.denx.de (ftp.denx.de)|85.214.49.3|:443... connected.
ERROR: The certificate of ‘ftp.denx.de’ is not trusted.
ERROR: The certificate of ‘ftp.denx.de’ has expired.
That's probably because we are still using an old distribution as the
base image to do the run in the CI.
We have a patch pending to update that image. It has just been promoted
to the top of my list of patches to look at today...
> Updating
> the U-Boot version should fix it and it doesn't hurt to use the latest
> U-Boot anyway.
Agreed, although that will still fail in the CI, until we bump to newer
components.
> Signed-off-by: David Lechner <david@lechnology.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> configs/lego_ev3_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configs/lego_ev3_defconfig b/configs/lego_ev3_defconfig
> index b4a1000036..555a63e36c 100644
> --- a/configs/lego_ev3_defconfig
> +++ b/configs/lego_ev3_defconfig
> @@ -43,7 +43,7 @@ BR2_TARGET_ROOTFS_SQUASHFS4_XZ=y
> BR2_TARGET_UBOOT=y
> BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
> BR2_TARGET_UBOOT_CUSTOM_VERSION=y
> -BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2018.11"
> +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2021.07"
> BR2_TARGET_UBOOT_BOARD_DEFCONFIG="legoev3"
>
> # host
> --
> 2.25.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-17 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 21:36 [Buildroot] [PATCH] configs/lego_ev3: update to U-Boot 2021.07 David Lechner
2021-10-17 8:15 ` Yann E. MORIN [this message]
2021-10-22 18:46 ` Peter Korsgaard
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=20211017081523.GE2400@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=david@lechnology.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