public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/bctoolbox: disable mbedtls support
Date: Thu, 10 Jul 2025 10:28:20 +0200	[thread overview]
Message-ID: <20250710102820.699bcea2@windsurf> (raw)
In-Reply-To: <20250710081059.482390-1-thomas.perale@mind.be>

Hello,

On Thu, 10 Jul 2025 10:10:58 +0200
Thomas Perale <thomas.perale@mind.be> wrote:

> They did add support for mbedtls 3.6 in commit [1].

Ah, I missed that, thanks for spotting it! I found the issue about
mbedtls 3.x in their bug tracker, and since the issue was open I
assumed it wasn't fixed.

> This package and mongrel2 are the last packages that doesn't have compat with
> mbedtls 3.6.
> For mongrel2 though the package is not maintained anymore and there isn't any
> port upstream.

I have no problem with dropping packages that are unmaintained, either
upstream or in Buildroot. So feel free to drop mongrel2 and even
bctoolbox.

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

  reply	other threads:[~2025-07-10  8:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 21:16 [Buildroot] [PATCH] package/bctoolbox: disable mbedtls support Thomas Petazzoni via buildroot
2025-07-10  8:10 ` Thomas Perale via buildroot
2025-07-10  8:28   ` Thomas Petazzoni via buildroot [this message]
2025-08-29 21:55   ` Thomas Petazzoni via buildroot
2025-08-29 21:59     ` Thomas Petazzoni via buildroot
2025-08-30  7:16       ` Thomas Perale via buildroot

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=20250710102820.699bcea2@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.perale@mind.be \
    --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