QA (public)

Current status¶

This seems not to be an major issue inside template generator. The current version can apparently handle with this in some way. The question remains, if this is the ideal way.

As can be seen in SUSE:Maintenance:19483:242960, the template lists all packages versions inside the Packages: key. There is unfortunately no indication of which version belongs to which product. This is the only difference in such cases.

Packages: sbd = 1.4.1+20200807.883c2f8-3.14.2, sbd = 1.4.1+20200807.883c2f8-6.1, sbd = 1.4.1+20200807.883c2f8-7.1, sbd-devel = 1.4.1+20200807.883c2f8-7.1

The inconsistency check still works, but does the check per product only, so the should be only one version (build number included) of each package per product.

Possible improvement¶

I can identify two possibilities here:

1. Leave the functionality as is and handle the problem in the tooling
2. Update the template metadata section to list versions per product correctly and use this new information in the tooling

jbaier_cz wrote:

Current status¶

This seems not to be an major issue inside template generator. The current version can apparently handle with this in some way. The question remains, if this is the ideal way.

As can be seen in SUSE:Maintenance:19483:242960, the template lists all packages versions inside the Packages: key. There is unfortunately no indication of which version belongs to which product. This is the only difference in such cases.

Packages: sbd = 1.4.1+20200807.883c2f8-3.14.2, sbd = 1.4.1+20200807.883c2f8-6.1, sbd = 1.4.1+20200807.883c2f8-7.1, sbd-devel = 1.4.1+20200807.883c2f8-7.1

so it means it picked first or last version as valid, because we excepted only one package = version combination per package

The inconsistency check still works, but does the check per product only, so the should be only one version (build number included) of each package per product.

Possible improvement¶

I can identify two possibilities here:

1. Leave the functionality as is and handle the problem in the tooling

• this will be dirty

1. Update the template metadata section to list versions per product correctly and use this new information in the tooling

• yes this is the preferred solution

• there is another thing with template generator -> source.diff for all branches ?

osukup wrote:

• yes this is the preferred solution

I agree.

• there is another thing with template generator -> source.diff for all branches ?

Template generator actually uses osc api -X POST "/request/242960?cmd=diff" to get the source diff, so there is a concatenation of all source diffs inside the template directory (as returned from the OBS).

jbaier_cz wrote:

osukup wrote:

• yes this is the preferred solution

I agree.

• there is another thing with template generator -> source.diff for all branches ?

Template generator actually uses osc api -X POST "/request/242960?cmd=diff" to get the source diff, so there is a concatenation of all source diffs inside the template directory (as returned from the OBS).

OH , thx

which task would that be that you need this solved for? I don't see a blocked task in our backlog right now.

I understood from hrommel1 that the full support for "multiple package version in incident" would be nice to do but is not seen as critical as the amount of tasks using that approach are limited and workarounds exist.

If I am not mistaken, poo#93931 depends on this. Luckily, this does not seems like a complicated issue.