Hi,
On Tue, May 31, 2016 at 08:37:36AM +0100, Richard Purdie wrote:
> On Mon, 2016-05-30 at 18:20 +0300, Maxin B. John wrote:
> > 5.39 -> 5.40
> >
> > Signed-off-by: Maxin B. John <maxin.j...@intel.com>
> > ---
> > meta/recipes-connectivity/bluez5/{bluez5_5.39.bb => bluez5_5.40.bb}
> > | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> > rename meta/recipes-connectivity/bluez5/{bluez5_5.39.bb =>
> > bluez5_5.40.bb} (89%)
>
> I had this in master-next and suspect it caused:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-mips64/build
> s/448/steps/BuildImages/logs/stdio
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-qa-pam/build
> s/800/steps/BuildImages/logs/stdio
>
> and the world targets also showed some issues. There were other changes
> mixed in (particularly python3) and some builds succeeded so it could
> also be some kind of dependency race.
Please ignore that patch then. As you have mentioned, it could be some
kind of dependency race (couldnt re-create the failure in the local build)
I will send the bluez5 upgrade along with ofono after python(2->3) work.
> Cheers,
> Richard
Best Regards,
Maxin
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
