From: yannick.brosseau@gmail.com (Brosseau, Yannick)
Subject: [lttng-dev] Query about LTTng 2.0 Debian packages
Date: Thu, 28 Jun 2012 22:51:31 -0400 [thread overview]
Message-ID: <CAEzWAeK+hFJr7xY_JF5MLH4YVfOHYq_OxgnLOsm7cUvUtsDjUA@mail.gmail.com> (raw)
In-Reply-To: <20120629015815.GA22800@quintessa>
On Thu, Jun 28, 2012 at 9:58 PM, Jon Bernard <jbernard at debian.org> wrote:
> * Jon Bernard <jbernard at debian.org> wrote:
>> * Mathieu Desnoyers <mathieu.desnoyers at efficios.com> wrote:
>> > Hi Jon,
>> >
>> > I wanted to get in touch with you regarding LTTng 2.0 Debian packages.
>> > Is there anything we can do to help you getting those packages into
>> > Debian ? They have been out for a while now, and even Ubuntu picked them
>> > up. I understand that you are probably busy, hence my offer for help.
>>
>> I've just uploaded another package I've been working on and LTTng 2.0 packages
>> are next on my list. Give me a few days to get things sorted, I'll post an
>> update next week with my status.
>
> Is the 2.0 series indented to replace the existing UST, or should they be able
> to exist side-by-side? ?I'm inclined to think the new packages should replace
> the old ones, and thus prevent a user from having both installed at the same
> time, but wanted to check first.
Yes, the 2.0 should replace the old 0.x ones. The new lttng-ust
replace the old ust. Also you can replace the old lttctl with the new
lttng-tools.
> URCU is updated and I'm looking at UST/CTL now. I'll file ITPs for babeltrace
> and modules in the morning.
>
> --
> Jon
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Yannick Brosseau
yannickbrosseau.com
prev parent reply other threads:[~2012-06-29 2:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 1:26 Mathieu Desnoyers
2012-06-21 19:14 ` Jon Bernard
2012-06-29 1:58 ` Jon Bernard
2012-06-29 2:51 ` Brosseau, Yannick [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=CAEzWAeK+hFJr7xY_JF5MLH4YVfOHYq_OxgnLOsm7cUvUtsDjUA@mail.gmail.com \
--to=yannick.brosseau@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