From: "Jérémie Galarneau via lttng-dev" <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Cc: diamon-discuss@lists.linuxfoundation.org,
linux-trace-users@vger.kernel.org
Subject: [lttng-dev] [RELEASE] Babeltrace 2.0.5 - Amqui
Date: Tue, 23 May 2023 14:58:16 -0400 [thread overview]
Message-ID: <ZG0MyPrucP4x9VA4@efficios.com> (raw)
Hi everyone!
Today we're releasing the fifth patch-level release of Babeltrace 2.0
"Amqui".
What's new since Babeltrace 2.0.4?
==================================
This release contains a number of plug-in fixes. The full change log follows.
2023-05-23 Babeltrace 2.0.5 (World Turtle Day)
* bt2: honor build system compiler/linker preferences
* Fix: clear_string_field(): set first character to 0
* Fix: src.ctf.fs: Not resolving event common ctx
* debug-info: fix -Wenum-int-mismatch problem in copy_field_class_content_internal
* fix: pass exec-prefix to python bindings install
* fix: document proper Bison version requirement
* cli: use return value of g_string_free
* babeltrace2-query(1): erroneous parameter used in example
* Fix: tests: print real values in a fixed format
* Fix: bt2: autodisc: remove thread error while inserting status in map
* tests: src.ctf.fs: add test for metadata with invalid syntax
* tests: shorten names of session-rotation trace
* bt2: ignore -Wredundant-decls warning
* ctf: fix -Wformat-overflow error in ctf-meta-resolve.cpp
* ctf-writer: fix -Wformat-overflow errors in resolve.c
* Fix: src.text.details: use write_uint_prop_value to handle unsigned values in write_int_range
* Add `dev-requirements.txt` for pip
* Fix: src.ctf.lttng-live: consider empty metadata packet as retry
* Fix: ctf: wrongfully requiring CTF metadata signature for every section
* Fix: src.ctf.lttng-live: session closed before any metadata is received
* fix: obsolete warnings with autoconf >= 2.71
* fix: explicitly disable '-Wsuggest-attribute=format'
* fix: set stable branch in gitreview config
* Fix: ctf-writer: list of reserved keywords
* compiler warning cleanup: is_signed_type: compare -1 to 1
* Update working version to Babeltrace 2.0.5
Important links
===============
Babeltrace 2.0.5 tarball:
https://www.efficios.com/files/babeltrace/babeltrace2-2.0.5.tar.bz2
Babeltrace website:
https://babeltrace.org
Mailing list (for support and development):
`lttng-dev at lists.lttng.org`
IRC channel:
`#lttng` on `irc.oftc.net`
Git repository:
https://bugs.lttng.org/projects/babeltrace
GitHub project:
https://github.com/efficios/babeltrace
Continuous integration:
https://ci.lttng.org/view/Babeltrace/
Code review:
https://review.lttng.org/q/project:babeltrace
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
reply other threads:[~2023-05-23 18:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZG0MyPrucP4x9VA4@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=jeremie.galarneau@efficios.com \
--cc=linux-trace-users@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).