From: yann.morin@orange.com
To: Daniel Lang <dalang@gmx.at>
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: Fri, 11 Jul 2025 15:41:56 +0200 [thread overview]
Message-ID: <aHEUpPI69u41yIM3@yd-6wlzhs3> (raw)
In-Reply-To: <20250711132237.76597-1-dalang@gmx.at>
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?
Regards,
Yann E. MORIN.
> 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
--
____________
.-----------------.--------------------: _ :------------------.
| Yann E. MORIN | Real-Time Embedded | __/ ) | /"\ ASCII RIBBON |
| | Software Designer | _/ - /' | \ / CAMPAIGN |
| +33 638.411.245 '--------------------: (_ `--, | X AGAINST |
| yann.morin (at) orange.com |_=" ,--' | / \ HTML MAIL |
'--------------------------------------:______/_____:------------------'
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-07-11 13:42 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 [this message]
2025-07-17 19:13 ` Daniel Lang 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=aHEUpPI69u41yIM3@yd-6wlzhs3 \
--to=yann.morin@orange.com \
--cc=buildroot@buildroot.org \
--cc=dalang@gmx.at \
--cc=julien.grossholtz@openest.io \
--cc=tuzakli.refik@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