From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next] package/hiawatha: update to 11.6
Date: Tue, 13 Aug 2024 20:25:30 +0200 [thread overview]
Message-ID: <20240813202530.4189cd25@windsurf> (raw)
In-Reply-To: <ZrsJ8SVroNPEWSXC@waldemar-brodkorb.de>
Hello Waldemar,
On Tue, 13 Aug 2024 09:23:29 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> > Would be OK for me. However, if upstream is not active anymore, should
> > we drop the package instead?
>
> He is still doing releases and added TLS 1.3 support recently.
> I would like to update it and keep the package. I can sent him an
> email to report the issue with TLS off and see what he says.
Then please report the issue with building without TLS support,
hopefully the maintainer will be interested in fixing what really is a
regression.
> Would you like two patches, one with URL updates for master and
> the update and TLS removal for next?
URL updates for master, for sure.
TLS removal, I would like to wait for the maintainer feedback. I'd
prefer to see it fixed instead.
Thanks!
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
prev parent reply other threads:[~2024-08-13 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 5:25 [Buildroot] [PATCH next] package/hiawatha: update to 11.6 Waldemar Brodkorb
2024-08-12 20:14 ` Thomas Petazzoni via buildroot
2024-08-13 6:58 ` Waldemar Brodkorb
2024-08-13 7:19 ` Thomas Petazzoni via buildroot
2024-08-13 7:23 ` Waldemar Brodkorb
2024-08-13 18:25 ` Thomas Petazzoni 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=20240813202530.4189cd25@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.org \
/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