From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/4] systemd: Remove items that made this machine (qemu) specific
Date: Sat, 20 Oct 2018 09:41:53 +0100 [thread overview]
Message-ID: <da0e5945e89cbee5712ecabf2409abcd7aa2fd8b.camel@linuxfoundation.org> (raw)
In-Reply-To: <20181017164326.67111-2-mark.hatle@windriver.com>
On Wed, 2018-10-17 at 12:43 -0400, Mark Hatle wrote:
> Create a new systemd-conf recipe to contain the specific
> system/machine
> configuration items. This new package is now machine specific.
>
> Without doing this trying to create a single system with multiple
> BSPs,
> one of which was qemu based, would result in the systemd -and-
> everything that
> dependend upon systemd to have their hash changed. The hash changing
> means
> lots of rebuilds, but worse if it's a package based system each
> different
> machine ends with a new PR value and a newly generated package.
>
> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
> ---
> meta/recipes-core/systemd/systemd-conf.bb | 51
> +++++++++++++++++++
> ...ange-the-default-device-timeout-to-2.patch | 35 -------------
> meta/recipes-core/systemd/systemd_239.bb | 28 ++++------
> 3 files changed, 60 insertions(+), 54 deletions(-)
> create mode 100644 meta/recipes-core/systemd/systemd-conf.bb
> delete mode 100644 meta/recipes-core/systemd/systemd/0001-core-
> device.c-Change-the-default-device-timeout-to-2.patch
Something in -next is causing:
https://autobuilder.yoctoproject.org/typhoon/#/builders/35/builds/92/steps/7/logs/step7c
which is a systemd boot timeout.
Note that I fixed up the selftest issue with the patch, I also added a
maintainers entry for systemd-conf to avoid another problem so please
use the patch in -next for any further revisions. We're going to need
more investigation to merge this though...
Cheers,
Richard
next prev parent reply other threads:[~2018-10-20 8:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 16:43 [PATCH 0/4] Fix a number of non-machine pkg hash change issues Mark Hatle
2018-10-17 16:43 ` [PATCH 1/4] systemd: Remove items that made this machine (qemu) specific Mark Hatle
2018-10-18 8:53 ` ChenQi
2018-10-18 15:37 ` Mark Hatle
2018-10-18 22:57 ` Richard Purdie
2018-10-20 8:41 ` Richard Purdie [this message]
2018-10-20 16:14 ` Mark Hatle
2018-10-17 16:43 ` [PATCH 2/4] mesa: Remove machine specific append Mark Hatle
2018-10-17 16:43 ` [PATCH 3/4] weston: " Mark Hatle
2018-10-18 10:24 ` Burton, Ross
2018-10-18 15:38 ` Mark Hatle
2018-10-19 10:51 ` Burton, Ross
2018-10-24 10:13 ` Mark Hatle
2018-10-25 8:36 ` Alexander Kanavin
2018-10-25 9:05 ` Martin Jansa
2018-10-25 9:26 ` Richard Purdie
2018-10-17 16:43 ` [PATCH 4/4] gstreamer: " Mark Hatle
2018-10-18 10:28 ` Richard Purdie
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=da0e5945e89cbee5712ecabf2409abcd7aa2fd8b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mark.hatle@windriver.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