Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org, Marek Belisko <marek.belisko@open-nandra.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/libblockdev: bump to version 3.6.0
Date: Sun, 15 Nov 2026 17:57:42 +0100	[thread overview]
Message-ID: <4cdb08bd211b972c750f4e11a8c33dee@free.fr> (raw)
In-Reply-To: <20261114210449.1550804-1-giulio.benetti@benettiengineering.com>

Hi Giulio,

On 14/11/2026 22:04, Giulio Benetti wrote:
> Release notes:
> https://github.com/storaged-project/libblockdev/releases/tag/3.6.0
> 
> The crypto plugin now uses libdevmapper directly, so add lvm2 to the
> dependencies of the crypto plugin (it was previously only pulled in
> indirectly through cryptsetup).
> 
> Refresh patch 0001 so it applies without fuzz.
> 
> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>

Considering this libblockdev is a bugfix-only and a security
update, I marked it as a "security bump" and applied it on
master (and next). However, the udisks bump seems more
significant, so I applied it only on next.

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-11-15 16:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14 21:04 [Buildroot] [PATCH 1/2] package/libblockdev: bump to version 3.6.0 Giulio Benetti
2026-11-14 21:04 ` [Buildroot] [PATCH 2/2] package/udisks: bump to version 2.12.0 Giulio Benetti
2026-11-15 16:57 ` 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=4cdb08bd211b972c750f4e11a8c33dee@free.fr \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=ju.o@free.fr \
    --cc=marek.belisko@open-nandra.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