From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [for-denzil][systemd update 0/6] Systemd updates
Date: Mon, 17 Sep 2012 19:09:38 +0200 [thread overview]
Message-ID: <k37lgg$ihf$1@ger.gmane.org> (raw)
In-Reply-To: <CAP9ODKqURDO6Am2mkBH8OdEQL=6JhZLga_-zgV7CX=GdDm6vmw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 17-09-12 15:31, Otavio Salvador schreef:
> On Mon, Sep 17, 2012 at 10:27 AM, Koen Kooi <koen@dominion.thruhere.net>
> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> Op 17-09-12 15:13, Otavio Salvador schreef:
>>> On Mon, Sep 17, 2012 at 7:58 AM, Koen Kooi
>>> <koen@dominion.thruhere.net> wrote:
>>>> A big update to systemd v189. Runtime tested on angstrom.
>>>>
>>>> This patchset depends on the bluez updates sent to the oe-core
>>>> list since bluez uses a deprecated udev API that went away
>>>> somewhere in between 182 and 189.
>>>
>>> This is a too big update for a stable branch in my point of view.
>>
>> It however is the only sane way to fix all the bugs users have reported
>> with system v44. I stopped with backporting patches after the stack
>> grew to 30+ patches.
>>
>> So what's your plan for getting the systemd bugs fixed in this branch?
>
> I think the backport is the only option;
I trust upstream releases more than my ability to do backports TBH
> how you tested it against regressions?
By running the same production tests as always. Bootup, shutdown, GUI,
adding services, removing them, inspecting the logs, things like that.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFQV1lSMkyGM64RGpERAuBtAKCFzScChycnk3CG9XYEffGeubRqiACeMb1j
v0is/KhDzrIQtORpLSBqJlg=
=8jRm
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-09-17 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 10:58 [for-denzil][systemd update 0/6] Systemd updates Koen Kooi
2012-09-17 10:58 ` [for-denzil][systemd update 1/6] systemd-systemctl-native: Add additional messages for better debugging Koen Kooi
2012-09-17 10:58 ` [for-denzil][systemd update 2/6] systemd-systemctl-native: extend systemctl wrapper to support mask action Koen Kooi
2012-09-17 10:58 ` [for-denzil][systemd update 3/6] systemd-systemctl-native: handle ALIAS tag Koen Kooi
2012-09-17 10:58 ` [for-denzil][systemd update 4/6] meta-systemd: systemd-systemctl-native: Also add support for WantedBy=*.service Koen Kooi
2012-09-17 10:58 ` [for-denzil][systemd update 5/6] gdm: do not rely on dev-tty7.device Koen Kooi
2012-09-17 10:58 ` [for-denzil][systemd update 6/6] systemd: update to v189 Koen Kooi
2012-09-17 13:13 ` [for-denzil][systemd update 0/6] Systemd updates Otavio Salvador
2012-09-17 13:27 ` Koen Kooi
2012-09-17 13:31 ` Otavio Salvador
2012-09-17 17:09 ` Koen Kooi [this message]
2012-09-18 6:34 ` Holger Hans Peter Freyther
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='k37lgg$ihf$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@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.