From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2018.02 Mosquitto v1.4.15 : no CONNECT/CONNACK on libmosquitto
Date: Mon, 02 Apr 2018 14:41:09 +0200 [thread overview]
Message-ID: <87d0zhok62.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180402140041.647c3d06@windsurf> (Thomas Petazzoni's message of "Mon, 2 Apr 2018 14:00:41 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello,
> On Mon, 02 Apr 2018 12:19:56 +0200, Peter Korsgaard wrote:
>> Did that solve your problem?
> Alexis replied privately to me (he should have kept the mailing list in
> Cc). Here is what he said:
> ==
> Hi Thomas, thanks for your answer.
> Indeed, reverting the version bumping (and the no-ssl build fix
> introduced by 63dfbca2c3ad509504e9118a49d396210917b079), I can make it
> work in my case. Since I do not want to use a modified buildroot (the
> project is shared with a team), for now I will use an external
> mosquitto package (in a BR2_EXTERNAL) with version 1.4.14. I will try
> to bisect changes between 1.4.14 and 1.4.15 to find out why my
> application is failing with last version
Alexis, please report your issue to mosquitto upstream. 1.4.15 fixed
security issues so we cannot really revert it, but if there is a real
problem it should be reported so it gets fixed when we E.G. update to
1.4.16.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-04-02 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 15:46 [Buildroot] Buildroot 2018.02 Mosquitto v1.4.15 : no CONNECT/CONNACK on libmosquitto Alexis Lothoré
2018-03-27 19:02 ` Thomas Petazzoni
2018-04-02 10:19 ` Peter Korsgaard
2018-04-02 12:00 ` Thomas Petazzoni
2018-04-02 12:41 ` Peter Korsgaard [this message]
2018-04-02 21:11 ` Alexis Lothoré
2018-04-02 21:42 ` Peter Korsgaard
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=87d0zhok62.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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