From: Peter Korsgaard <peter@korsgaard.com>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: buildroot@buildroot.org,
Titouan Christophe <titouanchristophe@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/mosquitto: revert an upstream change in 2.0.20 breaking nonthread builds
Date: Mon, 9 Dec 2024 20:53:03 +0100 [thread overview]
Message-ID: <b8d9b247-6dc2-4193-b4fc-8a3feb0537cd@korsgaard.com> (raw)
In-Reply-To: <Z1csc2aGtuzcsuwm@colin-ia-desktop>
On 12/9/24 18:44, Colin Foster wrote:
> Hi Peter,
>
> On Mon, Dec 09, 2024 at 10:23:08AM +0100, Peter Korsgaard wrote:
>>
>> > Committed to 2024.02.x and 2024.08.x, thanks.
>>
>> Ehh, I should have naturally FIRST bumped to mosquitto 2.0.20 before
>> doing that. This means that mosquitto is broken in 2024.02.9 /
>> 2024.08.3, sorry about that :(
>
> Out of curiosity, will there be a quick 2024.02.10 release with this or
> will that come in the standard release cadence next month?
How annoying is it? Are you using the git repo or a tarball? If git
tree, can you use the 2024.02.9 tag + 1 commit instead?
If needed, then I can do an early 2024.02.10 release, but it naturally
has some overhead so I would prefer not to.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-12-09 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 7:43 [Buildroot] [PATCH] package/mosquitto: revert an upstream change in 2.0.20 breaking nonthread builds Peter Korsgaard
2024-12-07 9:51 ` Peter Korsgaard
2024-12-08 14:49 ` Peter Korsgaard
2024-12-09 9:23 ` Peter Korsgaard
2024-12-09 17:44 ` Colin Foster
2024-12-09 19:53 ` Peter Korsgaard [this message]
2024-12-09 20:01 ` Colin Foster
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=b8d9b247-6dc2-4193-b4fc-8a3feb0537cd@korsgaard.com \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=colin.foster@in-advantage.com \
--cc=titouanchristophe@gmail.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