Hello,

avahi-ui-0.6.30 recipe appears in both openembedded-core and
meta-openembedded, is this intended and if so why? I do not see it doing
things differently.

The first one seems better maintained, the one in meta-openembedded has
MD5/SHA sums.

With todays GIT pull of both layers (meta-oe on top of oe-core), I run into
this problem:

-----
NOTE: package avahi-ui-0.6.30-r0: task do_fetch: Started
ERROR: Function 'Fetcher failure for URL:
'file://fix_for_automake_1.11.2.patch'. Unable to fetch URL
file://fix_for_automake_1.11.2.patch from any source.' failed
ERROR: Logfile of failure stored in:
/home/leon/sandbox/sidebranch/openembedded/imx53qsb/openembedded/build/tmp-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/avahi-ui-0.6.30-r0/temp/log.do_fetch.27184
Log data follows:
| DEBUG: Trying PREMIRRORS
| DEBUG: Trying Upstream
| ERROR: Function 'Fetcher failure for URL:
'file://fix_for_automake_1.11.2.patch'. Unable to fetch URL
file://fix_for_automake_1.11.2.patch from any source.' failed
ERROR: Task 2836
(/home/leon/sandbox/sidebranch/openembedded/imx53qsb/openembedded/meta-openembedded.git/meta-oe/recipes-connectivity/avahi/
avahi-ui_0.6.30.bb, do_fetch) failed with exit code '1'

meld ../openembedded-core.git/meta/recipes-connectivity/avahi/
avahi-ui_0.6.30.bb../meta-openembedded.git/meta-oe/recipes-connectivity/avahi/
avahi-ui_0.6.30.bb
-----

I cannot spot the error, other than that the patch exists in oe-core, but
it required from meta-oe. That should work, shouldn't it?

Regards,

Leon.
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to