All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: James Hilliard <james.hilliard1@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/python-service-identity: add missing python-cryptography dependency
Date: Wed, 10 Apr 2024 23:47:49 +0200	[thread overview]
Message-ID: <20240410234749.3ab49d42@windsurf> (raw)
In-Reply-To: <20240327162207.148920-1-romain.naour@smile.fr>

On Wed, 27 Mar 2024 17:22:07 +0100
Romain Naour <romain.naour@smile.fr> wrote:

> The last version bump removed python-pyopenssl runtime dependency but
> doing so also removed the python-cryptography runtime depdency [1] that
> is actually a direct runtime dependency.
> 
> While at it, update BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
> dependency comment.
> 
> [1] 6008f2b1b901be1374ac201b5e560cca61b4b61e
> 
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/6477656983 (TestPythonPy3ServiceIdentity)
> 
> Cc: James Hilliard <james.hilliard1@gmail.com>
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> ---
>  package/python-service-identity/Config.in | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

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

  reply	other threads:[~2024-04-10 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 16:22 [Buildroot] [PATCH] package/python-service-identity: add missing python-cryptography dependency Romain Naour
2024-04-10 21:47 ` Thomas Petazzoni via buildroot [this message]
2024-05-06 20:54 ` 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=20240410234749.3ab49d42@windsurf \
    --to=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=romain.naour@smile.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.