From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Multiple .bb files are due to be built which each provide udev
Date: Sat, 22 Dec 2012 10:03:18 +0100 [thread overview]
Message-ID: <20121222100318.14a48e10@eb-e6520> (raw)
In-Reply-To: <CAMBWrQ=J8n9tm99UT0QvcU1oB4kUtpH+kguDUYfxWP7_u_TPYQ@mail.gmail.com>
Hi Stan,
Le Fri, 21 Dec 2012 13:18:26 -0800,
Stan Hu <stanhu@gmail.com> a écrit :
> Thanks. Oops, I meant the denzil branch. It was updated today and has
> this bug you reference.
>
OK I now also reproduce this (my default images don't have udev so I
didn't saw that when testing denzil-next) in meta-toolchain-qte.
Here setting PREFERRED_PROVIDER_udev = "systemd"
workaround the problem (at least for meta-toolchain-qte but I'm
not using udev nor systemd so I can't really test if a rootfs using udev
still works this way) ?
The problem seems to come from :
6e0ddd4526f3e0005babe9381c17c06c22a9eda3
wheere commit log says "systemd: update to v189" but in reallity it also
adds udev packages in systemd recipe.
At first sight, I think I'll revert this patch as it will break denzil
builds which is not what we should expect from a stable branch.
Eric
next prev parent reply other threads:[~2012-12-22 9:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMBWrQnMQtEs78=OtkSR1mjctfet8ArQ_XE43wDB6-6NKiDShA@mail.gmail.com>
2012-12-21 20:58 ` Multiple .bb files are due to be built which each provide udev Stan Hu
2012-12-21 21:11 ` Martin Jansa
2012-12-21 21:18 ` Stan Hu
2012-12-22 9:03 ` Eric Bénard [this message]
2012-12-22 10:10 ` Koen Kooi
2012-12-22 11:05 ` Eric Bénard
2012-12-23 14:47 ` Eric Bénard
2012-12-23 18:10 ` Koen Kooi
2012-12-23 18:15 ` Eric Bénard
2012-12-23 18:53 ` Eric Bénard
2012-12-23 19:36 ` Koen Kooi
2012-12-23 21:21 ` Eric Bénard
2012-12-23 22:16 ` Koen Kooi
2012-12-24 8:06 ` Eric Bénard
2012-12-24 8:39 ` 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=20121222100318.14a48e10@eb-e6520 \
--to=eric@eukrea.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox