public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Andrew Shadura <andrew.shadura@collabora.co.uk>,
	Ross Burton <ross.burton@intel.com>
Cc: OE Core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3 2/3] dbus: update the recipes to 1.10.2
Date: Fri, 08 Jan 2016 15:50:58 +0100	[thread overview]
Message-ID: <1452264658.17716.21.camel@intel.com> (raw)
In-Reply-To: <5b0777dd5f120c6235dad62bab0dd8972a7c54be.1448029554.git.andrew.shadura@collabora.co.uk>

Hello!

I've tried this together with the user session patches on top of poky
0f3ad7c77a (almost the latest), without problems (except the checksum
problem that Ross already noticed). My local.conf had:

DISTRO_FEATURES_append = " systemd pam"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = ""
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
PACKAGECONFIG_append_pn-dbus = " user-session"

I also tried without pam and without user-session, again without
problems.

https://github.com/pohly/poky/tree/dbus

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  parent reply	other threads:[~2016-01-08 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 14:27 [PATCH v3 1/3] dbus: merge .bb and .inc Andrew Shadura
2015-11-20 14:27 ` [PATCH v3 2/3] dbus: update the recipes to 1.10.2 Andrew Shadura
2015-11-24 15:17   ` Burton, Ross
2016-01-08 14:50   ` Patrick Ohly [this message]
2015-11-20 14:27 ` [PATCH v3 3/3] dbus: add apparmor support Andrew Shadura
2015-12-02 16:27 ` [PATCH v3 1/3] dbus: merge .bb and .inc Patrick Ohly
2015-12-02 16:47   ` Burton, Ross
2015-12-03  7:46     ` Patrick Ohly
2015-12-03  8:39       ` Burton, Ross
2015-12-03  9:56         ` Patrick Ohly

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=1452264658.17716.21.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=andrew.shadura@collabora.co.uk \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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