From: jbernard@debian.org (Jon Bernard)
Subject: [lttng-dev] LTTng packages in Debian sid out of sync
Date: Thu, 14 Nov 2013 15:45:49 -0500 [thread overview]
Message-ID: <20131114204549.GA26321@shaniqua> (raw)
In-Reply-To: <20131113170101.GA10480@shaniqua>
* Jon Bernard <jbernard at debian.org> wrote:
> * Yannick Brosseau <yannick.brosseau at gmail.com> wrote:
> > On 11/10/13 10:29, Mathieu Desnoyers wrote:
> > > ----- Original Message -----
> > >> From: "Jon Bernard" <jbernard@debian.org>
> > >> To: "Mathieu Desnoyers" <mathieu.desnoyers at efficios.com>
> > >> Cc: "St?phane Graber" <stgraber at ubuntu.com>, "Alexandre Montplaisir" <alexmonthy at voxpopuli.im>,
> > >> lttng-dev at lists.lttng.org
> > >> Sent: Sunday, November 10, 2013 10:21:50 AM
> > >> Subject: Re: [lttng-dev] LTTng packages in Debian sid out of sync
> > >>
> > >> * Mathieu Desnoyers <mathieu.desnoyers at efficios.com> wrote:
> > >>> Hi Jon,
> > >>>
> > >>> Thanks for the updates. Did you manage to get the upgrade path from
> > >>> older lttng versions to work, or do users still need to uninstall the
> > >>> old package manually ?
> > >> I'm working on the upgrade packages now.
> > > Great!
> > >
> > >> I also just noticed a build
> > >> failure on armel[1] for lttng-tools. It could be a debian-specific
> > >> problem in the compiler/toolchain, but I haven't had a chance to look
> > >> into it yet. Let me know if you have any thoughts about this.
> > > We've already hit this one:
> > >
> > > https://bugs.lttng.org/issues/640
> > >
> > Yes, I've hit it in the fedora packages.
> > I've simply disabled the hardening Fedora option, so this temporary fix
> > might need another way to do it in debian:
> > (What it does is removing the -fPIE flag from the build option on arm)
> >
> > http://pkgs.fedoraproject.org/cgit/lttng-tools.git/commit/?id=a9d92b43548ec807b3b5485be092711c4c97f835
>
> Yep, I'll have to do the same thing - should be easy enough.
>
> I've finished the ust upgrade packages, I need only to test the possible
> scenarios to make sure all is well and I can upload. And then I'll fix
> the arm issue.
I think I have fixed the upgrade path, packages have been uploaded and
fingers are crossed. If this works then it leaves only the arm build
failure - which is cake.
--
Jon
next prev parent reply other threads:[~2013-11-14 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <630558869.45441.1382211345502.JavaMail.zimbra@efficios.com>
[not found] ` <856849325.45462.1382211994767.JavaMail.zimbra@efficios.com>
[not found] ` <20131019211009.GA83292@helmut.local>
[not found] ` <300817690.45707.1382242504740.JavaMail.zimbra@efficios.com>
[not found] ` <20131020134521.GA97360@helmut.local>
[not found] ` <1084047903.45979.1382281219903.JavaMail.zimbra@efficios.com>
[not found] ` <20131020160434.GA2011@helmut.local>
2013-11-03 23:19 ` Jon Bernard
2013-11-10 14:52 ` Mathieu Desnoyers
2013-11-10 15:21 ` Jon Bernard
2013-11-10 15:29 ` Mathieu Desnoyers
2013-11-13 1:42 ` Yannick Brosseau
2013-11-13 17:01 ` Jon Bernard
2013-11-14 20:45 ` Jon Bernard [this message]
2013-11-12 15:39 ` David Goulet
2013-11-13 21:02 ` Jon Bernard
2013-11-13 21:09 ` David Goulet
2013-11-22 18:57 ` Jon Bernard
2013-11-22 19:02 ` Mathieu Desnoyers
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=20131114204549.GA26321@shaniqua \
--to=jbernard@debian.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