public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] systemd: Upgrade to 232
Date: Mon, 21 Nov 2016 19:51:07 -0800	[thread overview]
Message-ID: <fee9f44e-4dd3-9286-a1e2-2f4e5ca2a74b@gmail.com> (raw)
In-Reply-To: <CAJTo0LYgH6_T5Y-YO1Px5eyYFLiud9SQvG1vHGRoebwkhVhdKg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1071 bytes --]



On 11/18/16 4:38 AM, Burton, Ross wrote:
> 
> On 16 November 2016 at 17:47, Khem Raj <raj.khem@gmail.com
> <mailto:raj.khem@gmail.com>> 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
>     <https://github.com/systemd/systemd/issues/3810>
> 
>     Signed-off-by: Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>>
> 
> 
> Because systemd-boot basically include the systemd recipe, this breaks
> systemd-boot.
> 
> Can we think up a way to handle systemd/systemd-boot without breaking every
> upgrade?

Is it a runtime break ? I just built systemd-boot for turbot/64bit successfully
> 
> Ross


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

      parent reply	other threads:[~2016-11-22  3:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 17:47 [PATCH 1/5] systemd: Upgrade to 232 Khem Raj
2016-11-16 17:47 ` [PATCH 2/5] taglib: Update to 1.11.1 Khem Raj
2016-11-21 17:57   ` Burton, Ross
2016-11-22  3:46     ` Khem Raj
2016-11-22 10:44       ` Burton, Ross
2016-11-22 11:20         ` Burton, Ross
2016-11-22 16:34           ` Khem Raj
2016-11-16 17:47 ` [PATCH 3/5] musl: Update to latest on master Khem Raj
2016-11-16 17:47 ` [PATCH 4/5] cmake.bbclass: Set CXXFLAGS and CFLAGS Khem Raj
2016-11-16 17:47 ` [PATCH 5/5] binutils: Fix parsing of ppc apuinfo for spe Khem Raj
2016-11-18 12:38 ` [PATCH 1/5] systemd: Upgrade to 232 Burton, Ross
2016-11-18 17:35   ` Khem Raj
2016-11-22  3:51   ` Khem Raj [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=fee9f44e-4dd3-9286-a1e2-2f4e5ca2a74b@gmail.com \
    --to=raj.khem@gmail.com \
    --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