From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [OE-core] State of bitbake world, Failed tasks 2015-08-30
Date: Mon, 31 Aug 2015 16:48:04 +0300 [thread overview]
Message-ID: <55E45B14.2080908@linux.intel.com> (raw)
In-Reply-To: <CALbNGRTScmFfjhAU+PY3Y5ZKdpk0vK9f67Kdq+7BYvPdnVv-Fg@mail.gmail.com>
On 08/31/2015 04:32 PM, Andreas Müller wrote:
>> * /meta-openembedded/meta-gnome/recipes-gnome/epiphany/epiphany_2.30.6.bb, do_fetch
This recipe will be removed when the new epiphany shows up in oe-core.
>> * /meta-openembedded/meta-gnome/recipes-gnome/gnome-power-manager/gnome-power-manager_2.32.0.bb, do_compile
>> * /meta-openembedded/meta-gnome/recipes-gnome/gnome-settings-daemon/gnome-settings-daemon_2.32.1.bb, do_compile
These are probably due to removal of libnotify 0.6.0.
>> * /meta-openembedded/meta-gnome/recipes-gnome/nautilus/nautilus3_3.2.1.bb, do_fetch
> ^ how did this return to world?
It was previously excluded because it was not compatible with libnotify
0.6.0. Now that it's gone, there is no reason to exclude it from world.
The fetch failure is because I somehow overlooked the recipe when fixing
the default tarball compression in gnome recipes. It needs a checksum
update.
Alex
next prev parent reply other threads:[~2015-08-31 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 12:56 State of bitbake world, Failed tasks 2015-08-30 Martin Jansa
2015-08-31 13:32 ` Andreas Müller
2015-08-31 13:32 ` [oe] " Andreas Müller
2015-08-31 13:48 ` Alexander Kanavin [this message]
2015-08-31 16:03 ` Martin Jansa
2015-08-31 16:03 ` [oe] " Martin Jansa
2015-09-02 11:16 ` [OE-core] " Richard Purdie
2015-09-02 11:16 ` Richard Purdie
2015-09-02 12:06 ` [OE-core] " Martin Jansa
2015-09-02 12:06 ` Martin Jansa
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=55E45B14.2080908@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--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 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.