Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [Consolidated Pull 00/21] Various Patches & some updates
Date: Fri, 07 Feb 2014 17:22:28 +0000	[thread overview]
Message-ID: <1391793748.32614.48.camel@ted> (raw)
In-Reply-To: <cover.1391791450.git.sgw@linux.intel.com>

On Fri, 2014-02-07 at 08:55 -0800, Saul Wold wrote:
> This patch set has been through the Autobuilder, the current failures
> related to the kernel update as we had a clean master build prior to this.

I'm not 100% convinced exactly which patches in the test build called
which failures.

> The following changes since commit cda502815c6acf789e1a0db7a7a1a7015b4ef71d:
> 
>   build-appliance-image: Update to poky commit b37dd451a52622d5b570183a81583cc34c2ff555 (2014-02-06 15:36:47 +0000)
> 
> are available in the git repository at:
> 
>   git://git.openembedded.org/openembedded-core-contrib sgw/stage
>   http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/stage
> 
> Alexandre Belloni (1):
>   matchbox-keyboard: daemonize launch

I'd keep meaning to ask someone about this, I'm not 100% sure its the
right thing to do or if there is another underlying issue which should
be fixed instead.

> Bruce Ashfield (1):
>   kernel: stop using -exec rm for deleting files

Did this trigger some of those failures?

> Chen Qi (1):
>   initscripts: add initscripts-functions-dev package

This is horrid, we need to fix the root problems, not hack around it.

> Chong Lu (2):
>   acl: enable ptest support
>   attr: enable ptest support
> 
> Cristian Iorga (2):
>   sbc: upgrade to 1.2
>   bluez5: upgrade to 5.14
> 
> Fathi Boudra (1):
>   systemtap: add aarch64 support
> 
> Jason Plum (1):
>   meta/oe/lib/path.py - check mount points, not device

This will kill performance. I'd like to understand which paths can get
split over mounts. I suspect the end result is we'd not support such
split mounts. Or we need two functions, one which is mount safe and one
which is not.

> Kai Kang (1):
>   eglibc-dbg: provides libc6-dbg

No, see Phil's comments.

> Khem Raj (1):
>   ossp-uuid: Use alternative source mirror
> 
> Koen Kooi (3):
>   systemd 208: move stray /usr/lib/systemd/* into /lib/systemd
>   openssh: package sshd PAM config inside openssh-sshd package
>   openssh: drag in required PAM modules.
> 
> Martin Jansa (1):
>   package.bbclass: add SHLIBSSEARCHDIRS to define where to search for
>     shlib providers

See Martin's comment, we need to fix this one in a better way.

> Paul Eggleton (1):
>   classes/populate_sdk_base: remove nostamp from do_populate_sdk
> 
> Randy MacLeod (1):
>   jpeg and directfb: cosmetic, fix perms for patches
> 
> Saul Wold (1):
>   rootfs_deb: Fix whitespace issue
> 
> Stefan Stanacar (3):
>   testimage: add ability to export tests
>   lib/oeqa: add module for running tests outside of the build system
>   oeqa/utils: targetbuild: don't use bb.fetch anymore

Cheers,

Richard



      parent reply	other threads:[~2014-02-07 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 16:55 [Consolidated Pull 00/21] Various Patches & some updates Saul Wold
2014-02-07 17:06 ` Martin Jansa
2014-02-07 17:22 ` Richard Purdie [this message]

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=1391793748.32614.48.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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