diff options
| -rw-r--r-- | debian/patches/series | 1 | ||||
| -rw-r--r-- | debian/salsa-ci.yml | 19 |
2 files changed, 20 insertions, 0 deletions
diff --git a/debian/patches/series b/debian/patches/series index 269d7690..17e9bdca 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -16,3 +16,4 @@ lib_security_multiarch_compat nullok_secure-compat.patch pam_mkhomedir_stat_before_opendir 0018-Libpam-is-both-shared-and-static.patch + diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml new file mode 100644 index 00000000..cbc91f4f --- /dev/null +++ b/debian/salsa-ci.yml @@ -0,0 +1,19 @@ +--- +include: + - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml + +# Piuparts currently fails on: +# ERROR: FAIL: After purging files have been modified: +# /usr/sbin/unix_chkpwd owned by: libpam-modules-bin +# Modified(user, group, mode, size, target): /usr/sbin/unix_chkpwd +# expected(root, shadow, - 100600, 43256, None) != found(root, shadow, - 102755, 43256, None) +# This is due to customizations in override_dh_fixperms which piuparts does not +# handle, thus the result should just be ignored for now. +piuparts: + extends: .test-piuparts + allow_failure: true + +# If Salsa CI is not running at +# https://salsa.debian.org/%{project_path}/-/pipelines, ensure that +# https://salsa.debian.org/%{project_path}/-/settings/ci_cd has in field "CI/CD +# configuration file" filename "debian/salsa-ci.yml" |