From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Heiko Thiery <heiko.thiery@gmail.com>
Cc: buildroot@buildroot.org, "Fiona Klute" <fiona.klute@gmx.de>,
"Jan Kundrát" <jan.kundrat@cesnet.cz>
Subject: Re: [Buildroot] [PATCH 1/6] package/libyang: bump to version 3.4.2
Date: Sun, 29 Dec 2024 00:00:15 +0100 [thread overview]
Message-ID: <20241229000015.1a9d4011@windsurf> (raw)
In-Reply-To: <20241219152105.298310-1-heiko.thiery@gmail.com>
Hello Heiko,
On Thu, 19 Dec 2024 16:21:01 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> The LICENSE hash has to be updated due to copyright year change.
>
> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
I wanted to merge this with the new tests, but without the libnetconf2
bump as I reported some issues with it. However, it seems like this
libyang update and the libnetconf2 update need to be done in lockstep,
as the build of libnetconf2 version in Buildroot today with the updated
libyang fails:
/home/thomas/projets/outputs/TestNetopeer2/build/libnetconf2-2.1.28/src/log.c:140:5: error: too many arguments to function 'ly_set_log_clb'
140 | ly_set_log_clb(nc_ly_log_clb, 1);
| ^~~~~~~~~~~~~~
and some more errors clearly hitting at an API change.
Not much you can do about it, aside for making it clear in the commit
messages.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-12-28 23:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 15:21 [Buildroot] [PATCH 1/6] package/libyang: bump to version 3.4.2 Heiko Thiery
2024-12-19 15:21 ` [Buildroot] [PATCH 2/6] package/libnetconf2: bump to version 3.5.1 Heiko Thiery
2024-12-28 22:40 ` Thomas Petazzoni via buildroot
2024-12-30 9:59 ` Heiko Thiery
2024-12-19 15:21 ` [Buildroot] [PATCH 3/6] package/sysrepo: bump to version 2.11.7 Heiko Thiery
2024-12-19 15:21 ` [Buildroot] [PATCH 4/6] package/netopeer2: bump to version 2.2.31 Heiko Thiery
2024-12-19 15:21 ` [Buildroot] [PATCH 5/6] support/testing/tests/package/test_sysrepo.py: add new test Heiko Thiery
2024-12-19 15:21 ` [Buildroot] [PATCH 6/6] support/testing/tests/package/test_netopeer2.py: " Heiko Thiery
2024-12-28 23:02 ` Thomas Petazzoni
2024-12-30 10:23 ` Heiko Thiery
2024-12-28 23:00 ` 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=20241229000015.1a9d4011@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=heiko.thiery@gmail.com \
--cc=jan.kundrat@cesnet.cz \
--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