From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [2011.03-maintenance][PATCH] gdk-pixbuf: add missing dependencies
Date: Wed, 12 Sep 2012 11:44:44 +0200 [thread overview]
Message-ID: <5050598C.2010805@dresearch-fe.de> (raw)
In-Reply-To: <CAJTo0LY5GyeesgKbsgjX8zRZSTrH=41UUey_9vGWg20A_fd-Gw@mail.gmail.com>
On 11.09.2012 15:39, Burton, Ross wrote:
> On 11 September 2012 14:03, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
>>> oe-core master has 2.24.1 at the moment, is there a good reason why
>>> meta-oe is hanging onto 2.10.14?
>>
>> This is the OE-Classic 2011.03-maintenance branch. I was surprised too until I
>> realised where this was :)
>
> Oh, wow. In that case I recommend either patching out those
> dependencies instead, or upgrading to a more modern version of
> gdk-pixbuf.
This is a maintenance branch. Tom normally does not accept upgrade patches if there's no critical problem it fixes.
I just wanted to fix a build problem introduced with Khem's commit.
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2012-09-12 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 22:50 [2011.03-maintenance][PATCH] gtk+_2.20.1: Depend on gdk-pixbuf-native Khem Raj
2012-08-31 21:07 ` Tom Rini
2012-09-06 12:17 ` Steffen Sledz
2012-09-10 6:00 ` Steffen Sledz
2012-09-11 12:42 ` [2011.03-maintenance][PATCH] gdk-pixbuf: add missing dependencies Steffen Sledz
2012-09-11 12:59 ` Burton, Ross
2012-09-11 13:02 ` Martin Jansa
2012-09-11 13:03 ` Paul Eggleton
2012-09-11 13:39 ` Burton, Ross
2012-09-12 9:44 ` Steffen Sledz [this message]
2012-09-14 22:07 ` Tom Rini
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=5050598C.2010805@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--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