Control: librabbitmq: New upstream releases (v0.14.0 - 2024-03-18) On Mon, Feb 13, 2023 at 03:29:39PM +0100, Florian Ernst wrote: > there is a new upstream release available which uscan did not detect, > cf. <https://github.com/alanxz/rabbitmq-c/releases>.
Updating this for the most recent release. The changes contain rabbitmq-c v0.14.0 Latest | Fixed | Fix potential stackoverflow in decoding table and array | Fix issue with Mach-O version (#758) | Make dependency on OpenSSL in rabbitmq-c.cmake match what is built (#725) | Fix pkg-config generation when CMAKE_INSTALL_DIR is absolute (#733) | Fix issue with amqp_basic_publish blocking in non-blocking mode (#780) | Fix SSL hostname check (#784) | Fix bug in amqp-consume documentation #791 | Changed | CMake minimum version is now 3.22 | OpenSSL minimum version is now 1.1.1 | Minimum TLS version supported is v1.2 (v1.3 is also supported). | OpenSSL ENGINE APIs are conditionally enabled based on availability | Added | Add option to read username/password from file in tools (#781) | Add amqp_ssl_socket_enable_default_verify_paths API to allow loading | from default certification paths | rabbitmq-c can be compiled against BoringSSL (#814) However, I can't help but wonder whether this package is in need of help: there are now three upstream releases not packaged yet, the oldest of which dating back to Feb 1, 2023 and the newest dating back to Mar 23, 2024 and containing a fix (#781, see above) for the RC bug #1037322, with a pointer to the required patch having already been added to that bugreport over year ago. Please comment on what your plans with respect to this package are, or whether you might need help. I could start packaging the new version, for instance, if that'd interest you. Given the current lack of feedback / activity (visible to me, that is, of course) I was / am considering to salvage this package, so please let me know what the current plans are. Cheers, Flo
signature.asc
Description: PGP signature
