From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, Fabio Urquiza <fabiorush@gmail.com>,
Bernd Kuhls <bernd@kuhls.net>
Subject: Re: [Buildroot] [PATCH 1/2] package/bitcoin: bump to version 28.0
Date: Sat, 26 Oct 2024 18:22:22 +0200 [thread overview]
Message-ID: <20241026182222.05359dbd@windsurf> (raw)
In-Reply-To: <20241013164759.3729983-1-ju.o@free.fr>
On Sun, 13 Oct 2024 18:47:58 +0200
Julien Olivain <ju.o@free.fr> wrote:
> For change log since 26.2, see:
> https://bitcoincore.org/en/releases/27.0/
> https://bitcoincore.org/en/releases/27.1/
> https://bitcoincore.org/en/releases/28.0/
>
> A notable change in version 28.0 is that bitcoin code now needs
> gcc >= 11.1. This change is reflected in the package Kconfig
> Config.in file.
>
> License file hash changed, due to year update in upstream commit:
> https://github.com/bitcoin/bitcoin/commit/1f8450f066724dfbb5c5bc4060843e2f3340ed88
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Patch tested in:
> https://gitlab.com/jolivain/buildroot/-/jobs/8072857206
> ---
> package/bitcoin/Config.in | 6 +++---
> package/bitcoin/bitcoin.hash | 8 ++++----
> package/bitcoin/bitcoin.mk | 2 +-
> 3 files changed, 8 insertions(+), 8 deletions(-)
Series applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-26 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 16:47 [Buildroot] [PATCH 1/2] package/bitcoin: bump to version 28.0 Julien Olivain
2024-10-13 16:47 ` [Buildroot] [PATCH 2/2] support/testing: package: bitcoin: fix test by increasing timeouts Julien Olivain
2024-11-11 15:56 ` Peter Korsgaard
2024-10-26 16:22 ` Thomas Petazzoni via buildroot [this message]
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=20241026182222.05359dbd@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=fabiorush@gmail.com \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.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