From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-cryptography: bump to version 46.0.5
Date: Sat, 07 Mar 2026 11:13:15 +0100 [thread overview]
Message-ID: <365eecbbd114508fa6d8ac0eb6a59a2f@free.fr> (raw)
In-Reply-To: <20260304175151.3660918-1-james.hilliard1@gmail.com>
HiJames,
On 04/03/2026 18:51, James Hilliard wrote:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Applied to master.
This minor bump was in fact a security update. I added the related
links. See:
https://gitlab.com/buildroot.org/buildroot/-/commit/9faac374c740e2dc1df32b47303a2e05ea7f5592
In the future, could you include the link to the changelog for such
security
oriented package, please?
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-03-07 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 17:51 [Buildroot] [PATCH 1/1] package/python-cryptography: bump to version 46.0.5 James Hilliard
2026-03-07 10:13 ` 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=365eecbbd114508fa6d8ac0eb6a59a2f@free.fr \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=ju.o@free.fr \
/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