From: Johan Hedberg <johan.hedberg@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: obexd 0.45 compilation problem
Date: Fri, 2 Mar 2012 08:02:58 -0800 [thread overview]
Message-ID: <20120302160258.GA18401@x220> (raw)
In-Reply-To: <1330701462.20578.21.camel@novo.hadess.net>
Hi Bastien,
On Fri, Mar 02, 2012, Bastien Nocera wrote:
> > >> > Trying to compile obexd 0.45 with bluez-4.98, I get:
> > >> > btio/btio.c: In function 'get_key_size':
> > >> > btio/btio.c:522:14: error: 'struct bt_security' has no member named 'key_size'
> > >> >
> > >> > Do you need to either up the bluez dependency, or is obexd lagging?
> > >> >
> > >> > Install log:
> > >> > http://koji.fedoraproject.org/koji/getfile?taskID=3846402&name=root.log
> > >> > Compile log:
> > >> > http://koji.fedoraproject.org/koji/getfile?taskID=3846402&name=build.log
> > >>
> > >> It is a known problem, until we are depending on a new release of
> > >> bluez (4.99) then we can add the build dependency properly, after that
> > >> we will probably have a new release for obexd as well.
> > >
> > > I don't understand. Are you telling me that obexd relies on an
> > > unreleased version of bluez?
> >
> > Not exactly obexd, but btio yes
>
> Given that btio is copy/pasted into obexd, it's obexd relying on an
> unreleased version of bluez.
>
> I could understand the idea if bluez hadn't had releases in ages, and
> you didn't have any control over it. But that's hardly helpful to the
> people downstream distributing your code.
This was obviously a mistake from our side. We didn't realize this
dependency was there. The right thing to do would have been to wait for
BlueZ 4.99 before pushing a new obexd release out.
Johan
next prev parent reply other threads:[~2012-03-02 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:43 obexd 0.45 compilation problem Bastien Nocera
2012-03-02 12:57 ` Luiz Augusto von Dentz
2012-03-02 14:13 ` Bastien Nocera
2012-03-02 15:06 ` Luiz Augusto von Dentz
2012-03-02 15:17 ` Bastien Nocera
2012-03-02 16:02 ` Johan Hedberg [this message]
2012-03-02 17:53 ` Marcel Holtmann
2012-03-02 18:09 ` Bastien Nocera
2012-03-02 18:11 ` Marcel Holtmann
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=20120302160258.GA18401@x220 \
--to=johan.hedberg@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.