Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Mattia Narducci <mattianarducci1@gmail.com>
Cc: buildroot@buildroot.org, James Hilliard <james.hilliard1@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/4] package/gensio: bump version to 3.0.4
Date: Sun, 30 Aug 2026 00:24:20 +0200	[thread overview]
Message-ID: <apNbdgIRuxlTeWB3@windsurf> (raw)
In-Reply-To: <20260816195616.279864-1-mattianarducci1@gmail.com>

Hello Mattia,

On Sun, Aug 16, 2026 at 09:56:06PM +0200, Mattia Narducci wrote:
> Changelog: https://sourceforge.net/p/ser2net/news
> 
> Static builds are no longer supported starting with version 2.6.0 [1]
> even when compiling all modules (gensios) in the library.
> 
> Updated licenses hashes due to upstream commit:
> https://github.com/cminyard/gensio/commit/859e4465cf5788cb99da1002a4c38cd8841c1bb7
> 
> Removed patch 0001 which is now upstream.
> 
> [1] https://github.com/cminyard/gensio/commit/7b3786f5fb733cd593e631a7b75d4b47f5a4b95f
> 
> Signed-off-by: Mattia Narducci <mattianarducci1@gmail.com>

Thanks a lot for your patch series, which I have applied to next. I
had to fix two things:

1. In both package/gensio/Config.in and package/ser2net/Config, add a
   Config.in comment about the dynamic library dependency

2. In PATCH 1/4, propagate the !BR2_STATIC_LIBS dependency to
   ser2net. You had done so in PATCH 4/4, but logically speaking, it
   belongs to PATCH 1/4, otherwise if we partially apply the series,
   or bisect through the commits, the situation between PATCH 1/4 and
   4/4 would be brokien

If you are interested by those two packages, don't hesitate to send a
patch adding yourself as a developer for them in the DEVELOPERS
file. This way you will receive e-mail notifications when there are
build failures, CVEs or new available upstream releases for those 2
packages.

Thanks a lot!

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

  parent reply	other threads:[~2026-08-29 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-16 19:56 [Buildroot] [PATCH 1/4] package/gensio: bump version to 3.0.4 Mattia Narducci
2026-08-16 19:56 ` [Buildroot] [PATCH 2/4] package/gensio: add udev optional dependency Mattia Narducci
2026-08-16 19:56 ` [Buildroot] [PATCH 3/4] package/gensio: add portaudio " Mattia Narducci
2026-08-16 19:56 ` [Buildroot] [PATCH 4/4] package/ser2net: bump version to 4.6.8 Mattia Narducci
2026-08-29 22:24 ` Thomas Petazzoni via buildroot [this message]
2026-09-03 20:25   ` [Buildroot] [PATCH 1/4] package/gensio: bump version to 3.0.4 Mattia Narducci

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=apNbdgIRuxlTeWB3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=mattianarducci1@gmail.com \
    --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