How to overwrite IMAGE_FSTYPES variable in loacal.conf using placement of kas file wic-targz-img.yml

How to overwrite IMAGE_FSTYPES variable in loacal.conf using placement of kas file wic-targz-img.yml

[Venkata.Pyla]

Hi,

I am trying to overwrite the IMAGE_FSTYPES variable with the values in wic-targz-img.yml by keeping at the end in kas file definition as shown in below command, but it is not overwriting.

$ kas-container build kas-cip.yml:kas/opt/ebg-swu.yml:kas/opt/wic-targz-img.yml

kas/opt/ebg-swu.yml include local_conf_header as below
-----------------------------------------
local_conf_header:
   ...
    wic-swu: |
         ...
          IMAGE_FSTYPES = "wic"
         ...
-----------------------------------------


kas/opt/wic-targz-img.yml include local_conf_header as below
-----------------------------------------
local_conf_header:
   ...
    image-type: |
         ...
          IMAGE_FSTYPES = "wic tar.gz"
         ...
-----------------------------------------

Final conf/local.conf generate as below
-----------------------------------------
# image-type
IMAGE_FSTYPES = "wic tar.gz"

...

# wic-swu
IMAGE_FSTYPES = "wic"
-----------------------------------------


Expecting conf/local.conf
-----------------------------------------
# wic-swu
IMAGE_FSTYPES = "wic"

...

# image-type
IMAGE_FSTYPES = "wic tar.gz"
-----------------------------------------

The above is possible when I use name with higher in alphabetical order like 'zimage-type:' in the wic-targz-img.yml
kas/opt/wic-targz-img.yml with 
-----------------------------------------
local_conf_header:
   ...
    zimage-type: |
         ...
          IMAGE_FSTYPES = "wic tar.gz"
         ...
-----------------------------------------

Is this the only solution to set the order of the variable assignment in local_conf_header?


Thanks,
Venkata.

Re: How to overwrite IMAGE_FSTYPES variable in loacal.conf using placement of kas file wic-targz-img.yml

[Jan Kiszka]

On 31.01.23 17:55, Venkata.Pyla@toshiba-tsip.com wrote:
> Hi,
> 
> I am trying to overwrite the IMAGE_FSTYPES variable with the values in wic-targz-img.yml by keeping at the end in kas file definition as shown in below command, but it is not overwriting.
> 
> $ kas-container build kas-cip.yml:kas/opt/ebg-swu.yml:kas/opt/wic-targz-img.yml
> 
> kas/opt/ebg-swu.yml include local_conf_header as below
> -----------------------------------------
> local_conf_header:
>    ...
>     wic-swu: |
>          ...
>           IMAGE_FSTYPES = "wic"
>          ...
> -----------------------------------------
> 
> 
> kas/opt/wic-targz-img.yml include local_conf_header as below
> -----------------------------------------
> local_conf_header:
>    ...
>     image-type: |
>          ...
>           IMAGE_FSTYPES = "wic tar.gz"
>          ...
> -----------------------------------------
> 
> Final conf/local.conf generate as below
> -----------------------------------------
> # image-type
> IMAGE_FSTYPES = "wic tar.gz"
> 
> ...
> 
> # wic-swu
> IMAGE_FSTYPES = "wic"
> -----------------------------------------
> 
> 
> Expecting conf/local.conf
> -----------------------------------------
> # wic-swu
> IMAGE_FSTYPES = "wic"
> 
> ...
> 
> # image-type
> IMAGE_FSTYPES = "wic tar.gz"
> -----------------------------------------
> 
> The above is possible when I use name with higher in alphabetical order like 'zimage-type:' in the wic-targz-img.yml
> kas/opt/wic-targz-img.yml with 
> -----------------------------------------
> local_conf_header:
>    ...
>     zimage-type: |
>          ...
>           IMAGE_FSTYPES = "wic tar.gz"
>          ...
> -----------------------------------------
> 
> Is this the only solution to set the order of the variable assignment in local_conf_header?
> 

local.conf nodes are alphabetically sorted as you already found out - we
should probably document that in kas. Generally spoken, you can make use
of that to achieve append behaviour, or you overwrite the original node
you are competing with.

In case of isar-cip-core, we can rearrange or kas option files so that
your use case becomes possible (though I'm unsure if it makes any sense:
the content of the tar.gz will be only a subset of the wic swupdate image).

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux

RE: [cip-dev] How to overwrite IMAGE_FSTYPES variable in loacal.conf using placement of kas file wic-targz-img.yml

[Venkata.Pyla]

>-----Original Message-----
>From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf
>Of Jan Kiszka
>Sent: 01 February 2023 13:06
>To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba-
>tsip.com>; cip-dev@lists.cip-project.org
>Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-
>tsip.com>; hayashi kazuhiro(林 和宏 □ＳＷＣ◯ＡＣＴ)
><kazuhiro3.hayashi@toshiba.co.jp>
>Subject: Re: [cip-dev] How to overwrite IMAGE_FSTYPES variable in loacal.conf
>using placement of kas file wic-targz-img.yml
>
>On 31.01.23 17:55, Venkata.Pyla@toshiba-tsip.com wrote:
>> Hi,
>>
>> I am trying to overwrite the IMAGE_FSTYPES variable with the values in wic-
>targz-img.yml by keeping at the end in kas file definition as shown in below
>command, but it is not overwriting.
>>
>> $ kas-container build
>> kas-cip.yml:kas/opt/ebg-swu.yml:kas/opt/wic-targz-img.yml
>>
>> kas/opt/ebg-swu.yml include local_conf_header as below
>> -----------------------------------------
>> local_conf_header:
>>    ...
>>     wic-swu: |
>>          ...
>>           IMAGE_FSTYPES = "wic"
>>          ...
>> -----------------------------------------
>>
>>
>> kas/opt/wic-targz-img.yml include local_conf_header as below
>> -----------------------------------------
>> local_conf_header:
>>    ...
>>     image-type: |
>>          ...
>>           IMAGE_FSTYPES = "wic tar.gz"
>>          ...
>> -----------------------------------------
>>
>> Final conf/local.conf generate as below
>> -----------------------------------------
>> # image-type
>> IMAGE_FSTYPES = "wic tar.gz"
>>
>> ...
>>
>> # wic-swu
>> IMAGE_FSTYPES = "wic"
>> -----------------------------------------
>>
>>
>> Expecting conf/local.conf
>> -----------------------------------------
>> # wic-swu
>> IMAGE_FSTYPES = "wic"
>>
>> ...
>>
>> # image-type
>> IMAGE_FSTYPES = "wic tar.gz"
>> -----------------------------------------
>>
>> The above is possible when I use name with higher in alphabetical
>> order like 'zimage-type:' in the wic-targz-img.yml
>> kas/opt/wic-targz-img.yml with
>> -----------------------------------------
>> local_conf_header:
>>    ...
>>     zimage-type: |
>>          ...
>>           IMAGE_FSTYPES = "wic tar.gz"
>>          ...
>> -----------------------------------------
>>
>> Is this the only solution to set the order of the variable assignment in
>local_conf_header?
>>
>
>local.conf nodes are alphabetically sorted as you already found out - we should
>probably document that in kas. Generally spoken, you can make use of that to
>achieve append behaviour, or you overwrite the original node you are
>competing with.
>
>In case of isar-cip-core, we can rearrange or kas option files so that your use
>case becomes possible (though I'm unsure if it makes any sense:
>the content of the tar.gz will be only a subset of the wic swupdate image).

Thanks for confirming,
I want to create swupdate image that should generate both tar.gz and wic image and use tar.gz for reproducibility checks.

I probably have to modify this file kas/opt/swupdate.yml to include both in IMAGE_FSTYPES = "wic tar.gz".

>
>Jan
>
>--
>Siemens AG, Technology
>Competence Center Embedded Linux

Re: RE: [cip-dev] How to overwrite IMAGE_FSTYPES variable in loacal.conf using placement of kas file wic-targz-img.yml

[Jan Kiszka]

On 01.02.23 12:39, Venkata.Pyla@toshiba-tsip.com wrote:
> 
> 
>> -----Original Message-----
>> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf
>> Of Jan Kiszka
>> Sent: 01 February 2023 13:06
>> To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba-
>> tsip.com>; cip-dev@lists.cip-project.org
>> Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-
>> tsip.com>; hayashi kazuhiro(林 和宏 □ＳＷＣ◯ＡＣＴ)
>> <kazuhiro3.hayashi@toshiba.co.jp>
>> Subject: Re: [cip-dev] How to overwrite IMAGE_FSTYPES variable in loacal.conf
>> using placement of kas file wic-targz-img.yml
>>
>> On 31.01.23 17:55, Venkata.Pyla@toshiba-tsip.com wrote:
>>> Hi,
>>>
>>> I am trying to overwrite the IMAGE_FSTYPES variable with the values in wic-
>> targz-img.yml by keeping at the end in kas file definition as shown in below
>> command, but it is not overwriting.
>>>
>>> $ kas-container build
>>> kas-cip.yml:kas/opt/ebg-swu.yml:kas/opt/wic-targz-img.yml
>>>
>>> kas/opt/ebg-swu.yml include local_conf_header as below
>>> -----------------------------------------
>>> local_conf_header:
>>>    ...
>>>     wic-swu: |
>>>          ...
>>>           IMAGE_FSTYPES = "wic"
>>>          ...
>>> -----------------------------------------
>>>
>>>
>>> kas/opt/wic-targz-img.yml include local_conf_header as below
>>> -----------------------------------------
>>> local_conf_header:
>>>    ...
>>>     image-type: |
>>>          ...
>>>           IMAGE_FSTYPES = "wic tar.gz"
>>>          ...
>>> -----------------------------------------
>>>
>>> Final conf/local.conf generate as below
>>> -----------------------------------------
>>> # image-type
>>> IMAGE_FSTYPES = "wic tar.gz"
>>>
>>> ...
>>>
>>> # wic-swu
>>> IMAGE_FSTYPES = "wic"
>>> -----------------------------------------
>>>
>>>
>>> Expecting conf/local.conf
>>> -----------------------------------------
>>> # wic-swu
>>> IMAGE_FSTYPES = "wic"
>>>
>>> ...
>>>
>>> # image-type
>>> IMAGE_FSTYPES = "wic tar.gz"
>>> -----------------------------------------
>>>
>>> The above is possible when I use name with higher in alphabetical
>>> order like 'zimage-type:' in the wic-targz-img.yml
>>> kas/opt/wic-targz-img.yml with
>>> -----------------------------------------
>>> local_conf_header:
>>>    ...
>>>     zimage-type: |
>>>          ...
>>>           IMAGE_FSTYPES = "wic tar.gz"
>>>          ...
>>> -----------------------------------------
>>>
>>> Is this the only solution to set the order of the variable assignment in
>> local_conf_header?
>>>
>>
>> local.conf nodes are alphabetically sorted as you already found out - we should
>> probably document that in kas. Generally spoken, you can make use of that to
>> achieve append behaviour, or you overwrite the original node you are
>> competing with.
>>
>> In case of isar-cip-core, we can rearrange or kas option files so that your use
>> case becomes possible (though I'm unsure if it makes any sense:
>> the content of the tar.gz will be only a subset of the wic swupdate image).
> 
> Thanks for confirming,
> I want to create swupdate image that should generate both tar.gz and wic image and use tar.gz for reproducibility checks.
> 
> I probably have to modify this file kas/opt/swupdate.yml to include both in IMAGE_FSTYPES = "wic tar.gz".
> 

To clarify again: What I meant is either aligning the node names in the
kas files or converting wic-targz-img.yml to targz-img.yml with
IMAGE_FSTYPES_append.

But I don't get yet why reproducibility checking is limited to tar.gz
outputs. Can't it be run against the common input, given that it works
only for the rootfs so far?

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux

RE: RE: [cip-dev] How to overwrite IMAGE_FSTYPES variable in loacal.conf using placement of kas file wic-targz-img.yml

[Venkata.Pyla]

>-----Original Message-----
>From: Jan Kiszka <jan.kiszka@siemens.com>
>Sent: 02 February 2023 14:27
>To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba-
>tsip.com>; cip-dev@lists.cip-project.org
>Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-
>tsip.com>; hayashi kazuhiro(林 和宏 □ＳＷＣ◯ＡＣＴ)
><kazuhiro3.hayashi@toshiba.co.jp>
>Subject: Re: RE: [cip-dev] How to overwrite IMAGE_FSTYPES variable in
>loacal.conf using placement of kas file wic-targz-img.yml
>
>On 01.02.23 12:39, Venkata.Pyla@toshiba-tsip.com wrote:
>>
>>
>>> -----Original Message-----
>>> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org>
>>> On Behalf Of Jan Kiszka
>>> Sent: 01 February 2023 13:06
>>> To: pyla venkata(ＴＳＩＰ TMIEC ODG Porting) <Venkata.Pyla@toshiba-
>>> tsip.com>; cip-dev@lists.cip-project.org
>>> Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-
>>> tsip.com>; hayashi kazuhiro(林 和宏 □ＳＷＣ◯ＡＣＴ)
>>> <kazuhiro3.hayashi@toshiba.co.jp>
>>> Subject: Re: [cip-dev] How to overwrite IMAGE_FSTYPES variable in
>>> loacal.conf using placement of kas file wic-targz-img.yml
>>>
>>> On 31.01.23 17:55, Venkata.Pyla@toshiba-tsip.com wrote:
>>>> Hi,
>>>>
>>>> I am trying to overwrite the IMAGE_FSTYPES variable with the values
>>>> in wic-
>>> targz-img.yml by keeping at the end in kas file definition as shown
>>> in below command, but it is not overwriting.
>>>>
>>>> $ kas-container build
>>>> kas-cip.yml:kas/opt/ebg-swu.yml:kas/opt/wic-targz-img.yml
>>>>
>>>> kas/opt/ebg-swu.yml include local_conf_header as below
>>>> -----------------------------------------
>>>> local_conf_header:
>>>>    ...
>>>>     wic-swu: |
>>>>          ...
>>>>           IMAGE_FSTYPES = "wic"
>>>>          ...
>>>> -----------------------------------------
>>>>
>>>>
>>>> kas/opt/wic-targz-img.yml include local_conf_header as below
>>>> -----------------------------------------
>>>> local_conf_header:
>>>>    ...
>>>>     image-type: |
>>>>          ...
>>>>           IMAGE_FSTYPES = "wic tar.gz"
>>>>          ...
>>>> -----------------------------------------
>>>>
>>>> Final conf/local.conf generate as below
>>>> -----------------------------------------
>>>> # image-type
>>>> IMAGE_FSTYPES = "wic tar.gz"
>>>>
>>>> ...
>>>>
>>>> # wic-swu
>>>> IMAGE_FSTYPES = "wic"
>>>> -----------------------------------------
>>>>
>>>>
>>>> Expecting conf/local.conf
>>>> -----------------------------------------
>>>> # wic-swu
>>>> IMAGE_FSTYPES = "wic"
>>>>
>>>> ...
>>>>
>>>> # image-type
>>>> IMAGE_FSTYPES = "wic tar.gz"
>>>> -----------------------------------------
>>>>
>>>> The above is possible when I use name with higher in alphabetical
>>>> order like 'zimage-type:' in the wic-targz-img.yml
>>>> kas/opt/wic-targz-img.yml with
>>>> -----------------------------------------
>>>> local_conf_header:
>>>>    ...
>>>>     zimage-type: |
>>>>          ...
>>>>           IMAGE_FSTYPES = "wic tar.gz"
>>>>          ...
>>>> -----------------------------------------
>>>>
>>>> Is this the only solution to set the order of the variable
>>>> assignment in
>>> local_conf_header?
>>>>
>>>
>>> local.conf nodes are alphabetically sorted as you already found out -
>>> we should probably document that in kas. Generally spoken, you can
>>> make use of that to achieve append behaviour, or you overwrite the
>>> original node you are competing with.
>>>
>>> In case of isar-cip-core, we can rearrange or kas option files so
>>> that your use case becomes possible (though I'm unsure if it makes any
>sense:
>>> the content of the tar.gz will be only a subset of the wic swupdate image).
>>
>> Thanks for confirming,
>> I want to create swupdate image that should generate both tar.gz and wic
>image and use tar.gz for reproducibility checks.
>>
>> I probably have to modify this file kas/opt/swupdate.yml to include both in
>IMAGE_FSTYPES = "wic tar.gz".
>>
>
>To clarify again: What I meant is either aligning the node names in the kas files
>or converting wic-targz-img.yml to targz-img.yml with
>IMAGE_FSTYPES_append.

Changing the node names should work, but I need to give irrelevant name just to increase the sorting order.
The other approach is use " IMAGE_FSTYPES_append" in all yaml files like "swupdate.yaml" and "targz-img.yml" because if one of the yaml file has "IMAGE_FSTYPES = " will replace the other if it comes later in the sorting order.

>
>But I don't get yet why reproducibility checking is limited to tar.gz outputs.
>Can't it be run against the common input, given that it works only for the
>rootfs so far?

Currently wic is not comparable with diffoscope, so I am checking only tar balls in reproducible build.

>
>Jan
>
>--
>Siemens AG, Technology
>Competence Center Embedded Linux