From: Daniel Lang via buildroot <buildroot@buildroot.org>
To: yann.morin@orange.com
Cc: buildroot@buildroot.org,
Julien Grossholtz <julien.grossholtz@openest.io>,
Refik Tuzakli <tuzakli.refik@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/paho-mqtt-cpp: bump to version 1.5.3
Date: Thu, 17 Jul 2025 21:13:20 +0200 [thread overview]
Message-ID: <e2ada059-8d9a-4c06-bfe4-1d56dbcb078c@gmx.at> (raw)
In-Reply-To: <aHEUpPI69u41yIM3@yd-6wlzhs3>
Hey Yann,
> Daniel, All,
>
> On 2025-07-11 15:22 +0200, Daniel Lang via buildroot spake thusly:
>> C++17 is required since 1.5.0.
>>
>> Signed-off-by: Daniel Lang <dalang@gmx.at>
>> ---
> [--SNIP--]
>> diff --git a/package/paho-mqtt-cpp/paho-mqtt-cpp.mk b/package/paho-mqtt-cpp/paho-mqtt-cpp.mk
>> index 2e0f409b96..0562cb0eb5 100644
>> --- a/package/paho-mqtt-cpp/paho-mqtt-cpp.mk
>> +++ b/package/paho-mqtt-cpp/paho-mqtt-cpp.mk
>> @@ -4,7 +4,7 @@
>> #
>> ################################################################################
>>
>> -PAHO_MQTT_CPP_VERSION = 1.3.2
>> +PAHO_MQTT_CPP_VERSION = 1.5.3
>
> The version history is a bit of a mess:
>
> - Tag 1.5.2 is dated 2025-06-25; points to a commit dated 2025-03-11;
> annotated tag;
>
> - Tag 1.5.3 is dated 2025-05-16; points to a commit dated 2025-05-15;
> un-annotated tag;
>
> - Graph-wise, commit 1.5.2 is before 1.5.3, though.
>
> - Commit 55833eb9fb1bf (Bumped version to v1.5.4) is dated 2025-06-25,
> the same day the 1.5.2 tag was comitted, but it contains a Changelog
> for "unrelased", not for 1.5.4, and porperly points to the current
> HEAD of master.
>
> It all looks like a bit of a mess. Could you see with upstream that they
> clarify the situation?
Thanks for bringing this up.
This is how I see it:
1.5.4 is definitely not released yet, there is still a milestone open [0] which seems to be
planed for July 25, 2025.
The 1.5.2 milestone [1] was closed on March 11. The same day of the tagged commit,
as you pointed out.
The 1.5.3 milestone [2] was closed on May 16. Again, same day as the tag.
1.5.3 is marked as "latest" release on Github [3].
So my assumption was, that they forgot to create the release for 1.5.2 or redid it.
>
> Regards,
> Yann E. MORIN.
Regards,
Daniel
[0]: https://github.com/eclipse-paho/paho.mqtt.cpp/milestone/18
[1]: https://github.com/eclipse-paho/paho.mqtt.cpp/milestone/15
[2]: https://github.com/eclipse-paho/paho.mqtt.cpp/milestone/16
[3]: https://github.com/eclipse-paho/paho.mqtt.cpp/releases/latest>
>> PAHO_MQTT_CPP_SITE = $(call github,eclipse,paho.mqtt.cpp,v$(PAHO_MQTT_CPP_VERSION))
>> PAHO_MQTT_CPP_LICENSE = EPL-2.0 or BSD-3-Clause
>> PAHO_MQTT_CPP_LICENSE_FILES = epl-v20 edl-v10
>> --
>> 2.50.1
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot@buildroot.org
>> https://lists.buildroot.org/mailman/listinfo/buildroot
>
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-07-17 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 13:22 [Buildroot] [PATCH] package/paho-mqtt-cpp: bump to version 1.5.3 Daniel Lang via buildroot
2025-07-11 13:41 ` yann.morin
2025-07-17 19:13 ` Daniel Lang 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=e2ada059-8d9a-4c06-bfe4-1d56dbcb078c@gmx.at \
--to=buildroot@buildroot.org \
--cc=dalang@gmx.at \
--cc=julien.grossholtz@openest.io \
--cc=tuzakli.refik@gmail.com \
--cc=yann.morin@orange.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