From: ChenQi <Qi.Chen@windriver.com>
To: Randy MacLeod <randy.macleod@windriver.com>,
Khem Raj <raj.khem@gmail.com>,
Philip Balister <philip@balister.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4 V2] systemd: Upgrade 219 -> 224
Date: Fri, 21 Aug 2015 18:14:20 +0800 [thread overview]
Message-ID: <55D6F9FC.9020807@windriver.com> (raw)
In-Reply-To: <55D682D9.4050902@windriver.com>
Hi Khem,
I built core-image-minimal for qemuarm64.
There's a lot of failures and warnings at boot time and the system boots
into rescue mode.
And I also verified 199 has no such problem.
Best Regards,
Chen Qi
On 08/21/2015 09:46 AM, Randy MacLeod wrote:
> On 2015-08-20 09:17 PM, Khem Raj wrote:
>> On Thu, Aug 20, 2015 at 6:04 AM, Philip Balister
>> <philip@balister.org> wrote:
>>> On 08/19/2015 10:21 PM, Khem Raj wrote:
>>>> On Wed, Aug 19, 2015 at 12:55 PM, Burton, Ross
>>>> <ross.burton@intel.com> wrote:
>>>>>
>>>>> On 17 August 2015 at 16:41, Khem Raj <raj.khem@gmail.com> wrote:
>>>>>>
>>>>>> There are many reasons, for me its overlay support for
>>>>>> systemd-nspawn,
>>>>>> networkd has got many new features that is now usable w.r.t. IP
>>>>>> forwarding,
>>>>>> vxlan etc.
>>>>>> and it has many bug fixed in those 2000 odd commits since 219, no
>>>>>> different then any other package upgrades we do in general it
>>>>>> keep the
>>>>>> upgrade workload lower as we roll the releases.
>>>>>> Any specific concerns ?
>>>>>
>>>>>
>>>>> Can we get an updated patch with a clearer commit log?
>>>
>>> I've also heard that as systemd evolves, more binaries are getting
>>> added
>>> to the base package that should be packaged separately for people
>>> interested in small images. I do not have personal experience here, but
>>> wanted to pass along the feedback.
>>>
>>> We should look at buildhistory packaging differences when we do
>>> upgrades.
>>
>> Here is the diff between files in 219 and 224, if you want to know
>> more I can paste more info just let me know.
>>
>> https://gist.github.com/kraj/2a066973a5e5cf83ed24
>>
>> sizes have gone up on daemons, no new daemons besides some new
>> service files
>> and scripts are added
>>
>
> ubu-15.10 will use v224 as well:
> http://cdimage.ubuntu.com/daily-live/current/wily-desktop-amd64.manifest
> and Arch and a couple other distro are using this version already:
> http://pkgs.org/download/systemd
>
> v224 was released 3 weeks ago:
> ---
> $ git log -1 v224
> commit b2a0ac5e5b29c73ca7c0da23369a4769d5a91ddd
> ...
> Date: Fri Jul 31 18:56:38 2015 +0200
> ---
>
> Khem's summary of the binaries is reassuring given that there
> has been lots of churn:
>
> $ git log --oneline v219..v224 | wc -l
> 2167
> $ git diff v219..v224 | diffstat | tail -1
> 1367 files changed, 109907 insertions(+), 166577 deletions(-)
>
> I'm skimming the NEWS file from 219->224 and I haven't seen
> anything that concerns me yet:
> https://github.com/systemd/systemd/blob/master/NEWS
> Qi,
> Please take a closer look at the NEWS file,
> review Khem's uprev and build and boot qemuarm64, qemuppc
> when you have time. Send partial feedback today even if you
> just review the commit and NEWS file.
>
> Qi may not be able to do that in the next couple of day
> due to SDK work.
>
> Khem,
> What testing have you done so far?
> Any ptest?
> What toolchain version are you building with, btw?
>
>
> It's late in M3 and we still have the kernel and toolchain coming in
> but unless we hear of known problems with v224, let's go for it
> once the new toolchain and kernel have settled.
>
next prev parent reply other threads:[~2015-08-21 10:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 5:03 [PATCH 2/4 V2] systemd: Upgrade 219 -> 224 Khem Raj
2015-08-17 12:42 ` Burton, Ross
2015-08-17 15:41 ` Khem Raj
2015-08-19 19:55 ` Burton, Ross
2015-08-20 2:21 ` Khem Raj
2015-08-20 13:04 ` Philip Balister
2015-08-21 1:17 ` Khem Raj
2015-08-21 1:46 ` Randy MacLeod
2015-08-21 1:55 ` Khem Raj
2015-08-21 10:14 ` ChenQi [this message]
2015-08-21 15:34 ` Khem Raj
2015-08-23 2: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=55D6F9FC.9020807@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philip@balister.org \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.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