From: Joan Lledó <[email protected]> The global RELEASE override makes every job build against unstable, even when debian/changelog targets a stable release.
Drop the global override so the other jobs follow the salsa-ci default (RELEASE_FROM_CHANGELOG), and keep RELEASE=unstable only in the shared Hurd build template so Hurd itself keeps building against unstable. Signed-off-by: Joan Lledó <[email protected]> --- pipeline-jobs.yml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/pipeline-jobs.yml b/pipeline-jobs.yml index 6a36ad7..600d3bb 100644 --- a/pipeline-jobs.yml +++ b/pipeline-jobs.yml @@ -3,9 +3,6 @@ include: - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml variables: - # Force this to avoid taking "unreleased" from the changelog. - # We don't have testing etc. anyway - RELEASE: unstable # This option is not supported SALSA_CI_BLHC_ARGS: --ignore-flag -fstack-clash-protection @@ -154,6 +151,10 @@ variables: extends: - .artifacts-default-expire variables: + # Hurd is only available in unstable, so always use it for Hurd builds, + # regardless of the target distribution in debian/changelog. Other jobs + # keep the salsa-ci default (RELEASE_FROM_CHANGELOG). + RELEASE: unstable DB_BUILD_PARAM: ${SALSA_CI_DPKG_BUILDPACKAGE_ARGS} DB_BUILD_TYPE: full script: -- 2.47.3
