Skip to contentSkip to conversation

waning "it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd"

DISCUSSION Andreas Oberritter 5 participants 7 messages Apr 17, 2012 – Apr 18, 2012

lore
Share & tools
lore
#0 lore raw

Hi,

the following warnings keep appearing on every fresh invocation of bitbake since a few months, I think:

WARNING: .../meta-oe/recipes-devtools/cloud9/cloud9_0.6.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
WARNING: .../meta-oe/recipes-connectivity/gateone/gateone_git.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
WARNING: .../meta/recipes-extended/lighttpd/lighttpd_1.4.30.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd

Is anybody working on fixing them? Is anybody else also seeing them, or is this likely caused by some missing variable in my distro conf? I am not using systemd.

Regards,
Andreas

#1 lore raw

2012/4/17 Andreas Oberritter <[email protected]>:

Quoted 5 lines

Hi,

the following warnings keep appearing on every fresh invocation of bitbake since a few months, I think:

Quoted 7 lines

WARNING: .../meta-oe/recipes-devtools/cloud9/cloud9_0.6.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
WARNING: .../meta-oe/recipes-connectivity/gateone/gateone_git.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
WARNING: .../meta/recipes-extended/lighttpd/lighttpd_1.4.30.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd

Is anybody working on fixing them? Is anybody else also seeing them, or is this likely caused by some missing variable in my distro conf? I am not using systemd.

Hi,
these warnings get created at recipe parsing time regardless of whether you are using Systemd or not,
so this is not a problem of your distro conf.

Don't know if anyone already has patches for them, but I see the warnings too.

Quoted 8 lines

Regards,
Andreas

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Signature · 2 lines
Regards
Samuel
#2 lore raw
In reply to Andreas Oberritter
Quoted 8 lines · Andreas Oberritter

Hi,

the following warnings keep appearing on every fresh invocation of bitbake since a few months, I think:

WARNING: .../meta-oe/recipes-devtools/cloud9/cloud9_0.6.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
WARNING: .../meta-oe/recipes-connectivity/gateone/gateone_git.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
WARNING: .../meta/recipes-extended/lighttpd/lighttpd_1.4.30.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd

yes they are there since systemd.bbclass rework, see
http://lists.linuxtogo.org/pipermail/openembedded-devel/2012-February/038011.html

Quoted 2 lines

Is anybody working on fixing them? Is anybody else also seeing them, or is this likely caused by some missing variable in my distro conf?

Not sure if someone is working on fixing them, but all is needed is to add ${PN}-systemd subpackage and add it to tasks which expects to get those apps with systemd support included.

Quoted 1 line

I am not using systemd.

It's pity that those are "parsing warnings" not QA warnings when packaging it - so that only people building them would see them, maybe Andreas Müller will reply why it's checked while parsing.

I'm using systemd but not cloud9|gateone|lighttpd.

Cheers,

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#3 lore raw

Op 17 apr. 2012, om 17:39 heeft Martin Jansa het volgende geschreven:

Quoted 8 lines · Andreas Oberritter
Quoted 7 lines

Hi,

the following warnings keep appearing on every fresh invocation of bitbake since a few months, I think:

WARNING: .../meta-oe/recipes-devtools/cloud9/cloud9_0.6.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
WARNING: .../meta-oe/recipes-connectivity/gateone/gateone_git.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd

The above 2 only have systemd support, so the WARNING is completely bogus and should be silenced.

#4 lore raw
Quoted 6 lines · Koen Kooi

Op 17 apr. 2012, om 17:39 heeft Martin Jansa het volgende geschreven:

Quoted 3 lines · Andreas Oberritter
Quoted 2 lines

Hi,

Quoted 7 lines
Quoted 5 lines
Quoted 5 lines

the following warnings keep appearing on every fresh invocation of bitbake since a few months, I think:

WARNING: .../meta-oe/recipes-devtools/cloud9/cloud9_0.6.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
WARNING: .../meta-oe/recipes-connectivity/gateone/gateone_git.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd

The above 2 only have systemd support, so the WARNING is completely bogus and should be silenced.

The warning is created in case the SYSTEMD_PACKAGES = "${PN}" instead of SYSTEMD_PACKAGES = "${PN}-systemd". Intention was to force the separation to keep systemd stuff out of images not supporting systemd. Problem with this: Images need to be changed e.g need to add gateone-systemd instead of gateone.

In the RFC for systemd.bbclass I suggested to make systemd a disto feature together with an automatic RDEPENDS for *-systemd packages. This was commented as no go [1]. The alternate suggestion making systemd as image feature ended up in nothing.

Another suggestion was made to separate out systemd into an own layer [2]. Guess this is not in due to release hysteria.

I faced similar situation with gtk-iconcache runonce [3]: In case a solution is not perfect it simply ends up in nothing although the current situation is not acceptable.

I lost interest making gurus happy so do what you want with it

Andreas
[1] http://lists.linuxtogo.org/pipermail/openembedded-devel/2012-February/037788.html
[2] http://lists.linuxtogo.org/pipermail/openembedded-devel/2012-April/038932.html
[3] http://lists.linuxtogo.org/pipermail/openembedded-core/2012-March/019760.html

#5 lore raw
In reply to Koen Kooi
Quoted 6 lines · Koen Kooi

Op 17 apr. 2012, om 17:39 heeft Martin Jansa het volgende geschreven:

Quoted 3 lines · Andreas Oberritter
Quoted 2 lines

Hi,

Quoted 7 lines
Quoted 5 lines
Quoted 5 lines

the following warnings keep appearing on every fresh invocation of bitbake since a few months, I think:

WARNING: .../meta-oe/recipes-devtools/cloud9/cloud9_0.6.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
WARNING: .../meta-oe/recipes-connectivity/gateone/gateone_git.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd

The above 2 only have systemd support, so the WARNING is completely bogus and should be silenced.

Another chapter of 'eat systemd or die'

Andreas

#6 lore raw

Op 18 apr. 2012, om 11:02 heeft Andreas Müller het volgende geschreven:

Quoted 7 lines · Koen Kooi
Quoted 6 lines

Op 17 apr. 2012, om 17:39 heeft Martin Jansa het volgende geschreven:

Quoted 3 lines · Andreas Oberritter
Quoted 2 lines

Hi,

Quoted 8 lines
Quoted 7 lines
Quoted 5 lines
Quoted 5 lines

the following warnings keep appearing on every fresh invocation of bitbake since a few months, I think:

WARNING: .../meta-oe/recipes-devtools/cloud9/cloud9_0.6.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd
WARNING: .../meta-oe/recipes-connectivity/gateone/gateone_git.bb: it is recommended to set SYSTEMD_PACKAGES as <existing-package>-systemd

The above 2 only have systemd support, so the WARNING is completely bogus and should be silenced.

Another chapter of 'eat systemd or die'

At the risk of feeding the troll: I've not seen anyone contribute decent sysv scripts for those recipes. So what is your point exactly?