From: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [RFT][PATCH] systemd: Upgrade to 232
Date: Mon, 14 Nov 2016 16:52:08 +0200 [thread overview]
Message-ID: <1479135128.4026.360.camel@linux.intel.com> (raw)
In-Reply-To: <20161110061149.20570-1-raj.khem@gmail.com>
On Wed, 2016-11-09 at 22:11 -0800, Khem Raj wrote:
> * Drop support for rcS.d SysV init scripts.
> These are prone to cause dependency loops, and almost all packages
> with
> rcS scripts now ship a native systemd service.
>
> * Drop mount propagation patch, it only happens with libseccomp, OE
> doesnt
> enable it
>
> * kdbus option has disappeared from configure
>
> * Ignore dev-so for PN now since systemd introduced private .so see
> https://github.com/systemd/systemd/issues/3810
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
I've "smoke"-tested systemd-resolved's new functionality: seems to work
as expected and I haven't noticed regressions so far in the rest of
SystemD.
BR,
Dmitry
next prev parent reply other threads:[~2016-11-14 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 6:11 [RFT][PATCH] systemd: Upgrade to 232 Khem Raj
2016-11-14 14:52 ` Dmitry Rozhkov [this message]
2016-11-21 12:57 ` Dmitry Rozhkov
2016-11-21 16:26 ` Khem Raj
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=1479135128.4026.360.camel@linux.intel.com \
--to=dmitry.rozhkov@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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