Skip to content

Actually propagate the osname from the sample recipes

Emanuele Aina requested to merge wip/em/osname-sample-recipes into apertis/v2022dev1

The sample recipes were not really propagating their custom osname to the included recipes, so they were still effectively using apertis.

To fix that, propagate the osname variable but also add a separate keyring variable to ensure that the apertis-archive-keyring gets used since we still want to access the Apertis APT repositories.

Merge request reports