From: Kristian Amlie <kristian.amlie@mender.io>
To: akuster808 <akuster808@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [krogoth] systemd network service fails to start on boot
Date: Mon, 29 Aug 2016 11:00:01 +0200 [thread overview]
Message-ID: <750bf9cc-ef3d-1ec0-6a48-604d20d85772@mender.io> (raw)
In-Reply-To: <57B22C24.2070604@gmail.com>
On 15/08/16 22:55, akuster808 wrote:
>
>
> On 08/15/2016 02:24 AM, Burton, Ross wrote:
>> On 15 August 2016 at 07:38, Kristian Amlie <kristian.amlie@mender.io> wrote:
>>
>>> So, I did what you asked. Is there anything else missing?
>>>
>>
>> No, just wait for the krogoth maintainer to pick up the patches.
>
> pulling to staging.
>
> thanks armin
So, any idea when this will end up in the krogoth branch? I see the
branch has moved forward, but this is still missing.
Systemd has been broken on krogoth for over a month now...
--
Kristian
prev parent reply other threads:[~2016-08-29 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 7:53 [krogoth] systemd network service fails to start on boot Kristian Amlie
2016-07-20 7:53 ` [PATCH 1/2] systemd: Create missing sysusers offline Kristian Amlie
2016-07-20 7:53 ` [PATCH 2/2] systemd: allow add users as a rootfs postprocess cmd Kristian Amlie
2016-08-09 8:59 ` [krogoth] systemd network service fails to start on boot Kristian Amlie
2016-08-09 10:01 ` Burton, Ross
2016-08-09 11:48 ` [krogoth] [PATCH 1/2] systemd: Create missing sysusers offline Kristian Amlie
2016-08-09 11:48 ` [krogoth] [PATCH 2/2] systemd: allow add users as a rootfs postprocess cmd Kristian Amlie
2016-08-15 6:38 ` [krogoth] systemd network service fails to start on boot Kristian Amlie
2016-08-15 9:24 ` Burton, Ross
2016-08-15 10:25 ` Kristian Amlie
2016-08-15 20:55 ` akuster808
2016-08-29 9:00 ` Kristian Amlie [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=750bf9cc-ef3d-1ec0-6a48-604d20d85772@mender.io \
--to=kristian.amlie@mender.io \
--cc=akuster808@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox