All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: RFC: systemd version - release or git?
Date: Wed, 19 Feb 2014 10:54:50 +0000	[thread overview]
Message-ID: <1392807290.14081.267.camel@ted> (raw)

As anyone looking at the autobuidler will know, we've been having a lot
of issues with instability with systemd tests under qemu.

I believe these are real world issues, most likely races in systemd
itself.

The last release of systemd, 208 was five months ago. There have been a
ton of changes since including many bug fixes.

Fedora 20 uses systemd 208 (the last release) with 200+ patches on top.

I'm therefore wondering if we shouldn't bite the bullet and add a git
recipe rather than trying to patch 208 into some form of life.

The proposal is therefore to add a more recent git recipe and make that
the default.

I have such a patch in master-next. I've debugged the toolchain issues,
missing kernel config and other issues with systemd master, it always
now seems to pass the autobuilder tests. I need to check on one
remaining automated QA test result to ensure its not a regression in
systemd.

Any objections to defaulting to a git version?

Cheers,

Richard




             reply	other threads:[~2014-02-19 10:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 10:54 Richard Purdie [this message]
2014-02-19 11:26 ` RFC: systemd version - release or git? Martin Jansa
2014-02-19 11:37   ` Anders Darander
2014-02-19 15:47     ` Richard Purdie
2014-02-20  6:52       ` Koen Kooi
2014-02-19 11:32 ` Koen Kooi

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=1392807290.14081.267.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.