From: Phil Blundell <philb@gnu.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
openembedded-devel@lists.openembedded.org,
openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Andrei Dinu : libffi upgrade to 3.0.11
Date: Sat, 15 Sep 2012 18:23:37 +0100 [thread overview]
Message-ID: <1347729817.4444.52.camel@x121e.pbcl.net> (raw)
In-Reply-To: <20120915162051.GA11051@jama.jama.net>
On Sat, 2012-09-15 at 18:20 +0200, Martin Jansa wrote:
> This changes .so name from libffi5 to libffi6, breaking every recipe
> depending on libffi when someone is using debian.bbclass.
How exactly do the recipes break? The whole point of debian.bbclass is
to avoid breakage when this happens by making libffi5 and libffi6
parallel installable. If that isn't working then there is clearly a bug
somewhere and we should fix that.
p.
next prev parent reply other threads:[~2012-09-15 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120914085706.2CBFC103C3@opal>
2012-09-15 16:20 ` [oe-commits] Andrei Dinu : libffi upgrade to 3.0.11 Martin Jansa
[not found] ` <CAK18fxGHn8aMu9Y926M2r9RQULR2VTOciBJkVD5S9awBV_j7-Q@mail.gmail.com>
2012-09-15 16:37 ` [O-core] " Martin Jansa
2012-09-17 10:57 ` Martin Jansa
2012-09-15 17:23 ` Phil Blundell [this message]
2012-09-15 17:28 ` Martin Jansa
2012-09-15 17:39 ` Martin Jansa
2012-09-15 20:39 ` Phil Blundell
2012-09-16 14:30 ` Martin Jansa
2012-09-16 18:47 ` [PATCH] recipes: bump PR to rebuild after libffi5 -> libffi6 Martin Jansa
2012-09-17 10:54 ` [PATCH] recipes: few more PR bumps " Martin Jansa
2012-09-17 17:17 ` [PATCH] libtelepathy: PR bump " Martin Jansa
2012-09-19 17:45 ` Saul Wold
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=1347729817.4444.52.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.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