From: Denys Dmytriyenko <denis@denix.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: How to fix warning: set SYSTEMD_PACKAGES as <existing-package>-systemd
Date: Fri, 04 May 2012 14:27:26 -0400 [thread overview]
Message-ID: <20120504182726.GA15097@denix.org> (raw)
In-Reply-To: <BEB5EFF4-B2E1-40DC-A12F-60ACB097C4E3@gmail.com>
On Fri, May 04, 2012 at 08:09:39PM +0200, Elvis Dowson wrote:
> Hi Koen,
>
> I bumped the PR, but still get the warning message. How is the warning for
> this specific package linked to its dependents. The warning looks localized
> to the lighttpd_1.4.30.bb recipe.
>
> If you can tell me how to fix it, I'll do it and send a patch.
You are trying to fix it in oe-core/poky layer, where it doesn't use systemd.
There is a .bbappend in meta-oe for that. In fact, here's what I told you
yesterday:
> WARNING: /tool/yocto/meta-openembedded/meta-oe/recipes-connectivity/networkmanager/networkmanager_0.9.2.0.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
> WARNING: /tool/yocto/poky/meta/recipes-extended/lighttpd/lighttpd_1.4.30.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
For these 2 please report them on openembedded-devel mailing list, where
meta-oe things are being discussed. The last warning is confisuing, as it
reports the recipe is in poky/oe-core, but it actually comes from the
corresponding .bbappend in meta-oe.
--
Denys
next prev parent reply other threads:[~2012-05-04 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 7:54 How to fix warning: set SYSTEMD_PACKAGES as <existing-package>-systemd Elvis Dowson
2012-05-04 8:02 ` Martin Jansa
2012-05-04 8:16 ` Elvis Dowson
2012-05-04 8:19 ` Martin Jansa
2012-05-04 9:19 ` Elvis Dowson
2012-05-04 9:46 ` Koen Kooi
2012-05-04 18:09 ` Elvis Dowson
2012-05-04 18:27 ` Denys Dmytriyenko [this message]
2012-05-04 18:52 ` Elvis Dowson
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=20120504182726.GA15097@denix.org \
--to=denis@denix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox