All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [oe-commits] Saul Wold : util-linux: Update to 2.22.1
Date: Mon, 03 Dec 2012 11:36:26 -0800	[thread overview]
Message-ID: <50BCFF3A.9010408@linux.intel.com> (raw)
In-Reply-To: <20121203191542.GG3354@jama.jama.net>

On 12/03/2012 11:15 AM, Martin Jansa wrote:
> On Mon, Dec 03, 2012 at 02:49:20PM +0000, git@git.openembedded.org wrote:
>> Module: openembedded-core.git
>> Branch: master
>> Commit: ac807121ce3ba965f3e2a4f664a60ae4e33ce550
>> URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=ac807121ce3ba965f3e2a4f664a60ae4e33ce550
>>
>> Author: Saul Wold <sgw@linux.intel.com>
>> Date:   Fri Nov 16 19:51:34 2012 +0000
>>
>> util-linux: Update to 2.22.1
>>
>> Fix the configure-sbindir test, which was not working correctly
>> add a patch to configure to correctly test if the prefixes are
>> conatined in libdir so they don't duplicate.
>>
>> Removed aarch64 patch since it been merged into this version
>>
>> Rebased util-linux-ng-replace-siginterrupt.patch
>
> This seems to autodetect systemd if available and cause some unpackaged
> files
>
> util-linux-2.22.1: util-linux: Files/directories were installed but not
> shipped
>    /lib/systemd
>    /lib/systemd/system
>    /lib/systemd/system/uuidd.socket
>    /lib/systemd/system/uuidd.service
>
> I should be resolved by meta-systemd, by adding bbappend (that's what I
> did for pcsc-lite doing the same).
>
> But maybe oe-core should explicitly disable systemd for meta-systemd to
> explicitly enable it back.
>
Sorry about that, I know that Khem also had some changes that I am 
looking at, I have not looked to see if they address the issue.

Sau!

> Cheers,
>
>>
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>>
>> ---
>>
>>   meta/recipes-core/util-linux/util-linux.inc        |   21 +++++++++++--------
>>   .../util-linux/add-aarch64-support.patch           |   18 -----------------
>>   .../util-linux/util-linux/configure-sbindir.patch  |   15 +++++++++----
>>   .../util-linux/util-linux/fix-configure.patch      |   20 +++++++++++++++++++
>>   .../util-linux/uclibc-__progname-conflict.patch    |   14 ++++++------
>>   .../util-linux-ng-replace-siginterrupt.patch       |   15 +++++++------
>>   .../{util-linux_2.21.2.bb => util-linux_2.22.1.bb} |   10 ++++----
>>   7 files changed, 62 insertions(+), 51 deletions(-)
>>
>> Diff:   http://git.openembedded.org/?p=openembedded-core.git/?a=commitdiff;h=ac807121ce3ba965f3e2a4f664a60ae4e33ce550
>>
>> _______________________________________________
>> Openembedded-commits mailing list
>> Openembedded-commits@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-commits
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



      reply	other threads:[~2012-12-03 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121203144920.55C841035D@opal>
2012-12-03 19:15 ` [oe-commits] Saul Wold : util-linux: Update to 2.22.1 Martin Jansa
2012-12-03 19:36   ` Saul Wold [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=50BCFF3A.9010408@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@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.