From: Markus Volk <f_l_k@t-online.de>
To: richard.purdie@linuxfoundation.org,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][RFC PATCH 1/2] libdecor: initial add recipe
Date: Sun, 22 May 2022 12:22:09 +0200 [thread overview]
Message-ID: <080bfcd8-afeb-39a6-6215-88ed6261cd8e@t-online.de> (raw)
In-Reply-To: <f304f84a8bb4bd353898d54cf1378b5c0084498e.camel@linuxfoundation.org>
Am 22.05.22 um 11:24 schrieb richard.purdie@linuxfoundation.org:
> What kind of issues? :/
During the build of a systemd-based image, eudev was added. Possibly I
was to blame for this by my own changes ;)
But after updating the master branch yesterday, I also got build aborts
for some python modules. I didn't investigate this further, but switched
to the kirkstone branch.
Markus
next prev parent reply other threads:[~2022-05-22 10:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 6:43 [meta-oe][RFC PATCH 1/2] libdecor: initial add recipe Markus Volk
2022-05-19 6:43 ` [meta-oe][RFC PATCH 2/2] libsdl2: rework and cleanup Markus Volk
2022-05-19 14:18 ` [OE-core] " Luca Ceresoli
2022-05-19 14:30 ` Markus Volk
2022-05-19 15:15 ` Alexander Kanavin
2022-05-19 16:43 ` [OE-core] [meta-oe][RFC PATCH 1/2] libdecor: initial add recipe Luca Ceresoli
2022-05-19 16:46 ` Alexander Kanavin
2022-05-19 19:42 ` Markus Volk
2022-05-19 19:59 ` Alexander Kanavin
2022-05-19 20:12 ` Markus Volk
2022-05-20 12:46 ` Markus Volk
2022-05-21 7:48 ` richard.purdie
2022-05-22 8:48 ` Markus Volk
2022-05-22 9:24 ` richard.purdie
2022-05-22 10:22 ` Markus Volk [this message]
2022-05-22 12:12 ` richard.purdie
2022-05-22 17:26 ` Markus Volk
2022-05-23 15:26 ` Markus Volk
2022-05-31 19:06 ` Markus Volk
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=080bfcd8-afeb-39a6-6215-88ed6261cd8e@t-online.de \
--to=f_l_k@t-online.de \
--cc=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.