systemd-conf bbappend not working (warrior)

systemd-conf bbappend not working (warrior)

[Visser Sander (2) (Consultant)]

Hi

In warrior there is systemd-conf_243.bb but in the build folder tmp/work the version is called 1.0-r0

If I create a systemd-conf_%.bbappend its content is not applied. For instance if I set PR = "r1" that has no affect. I am also unable to add tasks to modify the default configuration...

Any ideas why this is happening for this recipe alone?

/Regards Sander

This email message and any attachments may contain confidential information and may be privileged. If you are not the intended recipient or otherwise not authorized to receive this message, you are prohibited to use, copy, disclose or take any action based on this email or any information contained herein. If you are not the intended recipient, please advise the sender immediately by replying to this email and permanently delete this message and any attachments from your system.

Re: systemd-conf bbappend not working (warrior)

[Peter Kjellerstedt]

> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org <openembedded-
> devel-bounces@lists.openembedded.org> On Behalf Of Visser Sander (2)
> (Consultant)
> Sent: den 7 februari 2020 17:15
> To: openembedded-devel@lists.openembedded.org
> Subject: [oe] systemd-conf bbappend not working (warrior)
> 
> Hi
> 
> In warrior there is systemd-conf_243.bb but in the build folder tmp/work

In Warrior, the version of systemd-conf is 241, not 243. 

* What versions of what layers do your really have?
* Do you have any other layers than the layers in Poky?
* Are there any other bb or bbappends for systemd-conf in any of the 
  other layers?

> the version is called 1.0-r0

"1.0" is the default version if no version is set in the recipe name 
or using PV. Before Warrior, systemd-conf did not have an explicit 
version set and would then use "1.0" as version.

> If I create a systemd-conf_%.bbappend its content is not applied. For
> instance if I set PR = "r1" that has no affect. I am also unable to add
> tasks to modify the default configuration...
> 
> Any ideas why this is happening for this recipe alone?
> 
> /Regards Sander

//Peter

Re: systemd-conf bbappend not working (warrior)

[Visser Sander (2) (Consultant)]

Im on latest warrior. You are right - the systemd version is 241 and not 243 in warrior, but the systemd-conf package is built as 1.0-r0 despite recipe being systemd-conf_241.bb in warrior:4edf4eb9cc86fbd4b51240fae527c1b97a7ace74 poky.

Any ideas why tmp/work decides to build the recipe as 1.0-r0. That seems to be the reason for my systemd-conf_241.bbappend task/changes not being applied...

I have tried both a do_install_append() and inserting a task of my own before install to change the default configuration files. None of these changes are applied (it worked fine in sumo where config files are part of systemd recipe). If I name my bbappend  "_1.0" then bitbake complains it can not be applied, so bitbake at some level seems to know the version is supposed to be 241.

/Regards Sander

-----Original Message-----
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Sent: Friday, February 7, 2020 5:45 PM
To: Visser Sander (2) (Consultant) <sander.visser.2@consultant.volvo.com>; openembedded-devel@lists.openembedded.org
Subject: RE: systemd-conf bbappend not working (warrior)

> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org <openembedded-
> devel-bounces@lists.openembedded.org> On Behalf Of Visser Sander (2)
> (Consultant)
> Sent: den 7 februari 2020 17:15
> To: openembedded-devel@lists.openembedded.org
> Subject: [oe] systemd-conf bbappend not working (warrior)
>
> Hi
>
> In warrior there is systemd-conf_243.bb but in the build folder
> tmp/work

In Warrior, the version of systemd-conf is 241, not 243.

* What versions of what layers do your really have?
* Do you have any other layers than the layers in Poky?
* Are there any other bb or bbappends for systemd-conf in any of the
  other layers?

> the version is called 1.0-r0

"1.0" is the default version if no version is set in the recipe name or using PV. Before Warrior, systemd-conf did not have an explicit version set and would then use "1.0" as version.

> If I create a systemd-conf_%.bbappend its content is not applied. For
> instance if I set PR = "r1" that has no affect. I am also unable to
> add tasks to modify the default configuration...
>
> Any ideas why this is happening for this recipe alone?
>
> /Regards Sander

//Peter


This email message and any attachments may contain confidential information and may be privileged. If you are not the intended recipient or otherwise not authorized to receive this message, you are prohibited to use, copy, disclose or take any action based on this email or any information contained herein. If you are not the intended recipient, please advise the sender immediately by replying to this email and permanently delete this message and any attachments from your system.