All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org, "Alexis Lothoré" <alexis.lothore@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/openscap: propagate dependencies of libxmlsec1 after bump
Date: Sun, 13 Sep 2026 09:44:12 +0200	[thread overview]
Message-ID: <fd67340cdca90c98ec9833f851530b6b@free.fr> (raw)
In-Reply-To: <20260911063053.795160-1-thomas.petazzoni@bootlin.com>

On 11/09/2026 08:30, Thomas Petazzoni via buildroot wrote:
> In commit
> fef9cad1fe84b4366e705adb03470e12199ffd25 ("package/libxmlsec1: bump
> version to 1.3.12"), libxmlsec1 was bumped, and alongside some
> additional "depends on" were added.
> 
> However, these new "depends on" were not propagate to reverse
> dependencies of libxmlsec1, i.e. openscap, causing Kconfig warnings:
> 
> WARNING: unmet direct dependencies detected for BR2_PACKAGE_LIBXMLSEC1
>   Depends on [n]: BR2_TOOLCHAIN_GCC_AT_LEAST_7 [=n] && 
> BR2_TOOLCHAIN_HAS_ATOMIC [=n]
>   Selected by [y]:
>   - BR2_PACKAGE_OPENSCAP [=y] && BR2_PACKAGE_LIBGPG_ERROR_ARCH_SUPPORTS 
> [=y] && !BR2_STATIC_LIBS [=n] && BR2_TOOLCHAIN_HAS_THREADS_NPTL [=y]
> 
> and potentially some build issues, even though we didn't check in the
> autobuilders for potential failures.
> 
> This commit fixes that by properly propagating the new dependencies.
> 
> Cc: Alexis Lothoré <alexis.lothore@bootlin.com>
> Cc: Julien Olivain <ju.o@free.fr>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-09-13  7:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  6:30 [Buildroot] [PATCH] package/openscap: propagate dependencies of libxmlsec1 after bump Thomas Petazzoni via buildroot
2026-09-11  8:15 ` Alexis Lothoré via buildroot
2026-09-13  7:44 ` Julien Olivain 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=fd67340cdca90c98ec9833f851530b6b@free.fr \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.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 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.