archive mirror
 help / color / mirror / Atom feed
From: "Jérémie Galarneau" <>
Subject: [RELEASE] Babeltrace 2.0.1 - Amqui
Date: Tue, 4 Feb 2020 16:48:05 -0500	[thread overview]
Message-ID: <> (raw)

Hi everyone!

Today we're releasing the first patch-level release of Babeltrace 2.0

What's new since Babeltrace 2.0.0?
This release contains minor bug fixes which are mainly
related to packaging and documentation issues.

Of note for packagers, we have changed the autoconf package name to
`babeltrace2`. This fixes co-installation problems with Babeltrace
1.x, but also changes the naming scheme of the official tarball.

The official tarballs of Babeltrace 2 are now named
`babeltrace2-$VERSION.tar.bz2`. We have added a symlink to reflect
this naming scheme to the prior Babeltrace 2.0.0 release.

The full change log follows.

2020-02-04 Babeltrace 2.0.1
	* fix: Remove empty python bindings documentation
	* README: Babeltrace 2 was released in 2020
	* fix: set autoconf package name to babeltrace2
	* Typo: occured -> occurred
	* .gitignore: Add missing bt2/native_bt.d
	* fix: build failure on ppc64el with '-Werror=format-overflow='
	* Silence -Wnull-dereference warning in generated CTF parser code
	* plugin-so.c: add comment about why we're not using a GLib linked list
	* doc: graph.h: do not link to `` for `babeltrace(1)`
	* fix: common/list.h is LGPL-2.1
	* fix: build Python bindings with GCC10
	* fix: use correct function to print 'enum bt_ctf_scope'
	* Update working version to Babeltrace 2.0.1

Important links
Babeltrace 2.0.1 tarball:

Babeltrace website:

Mailing list (for support and development):
    `lttng-dev at`

IRC channel:
    `#lttng` on ``

Git repository:

GitHub project:

Continuous integration:

Code review:

                 reply	other threads:[~2020-02-04 21:48 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [RELEASE] Babeltrace 2.0.1 - Amqui' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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 NNTP newsgroup(s).