The purpose of this list is to monitor usage of SalsaCI, encourage using it and fix regressions if happened.
The packages listed below are the top ten installed ones according to Debian popularity contest:
coreutils: https://salsa.debian.org/gioele/coreutils/-/pipelines
- Uses Salsa CI.
- Lintian emits errors that are hard to fix.
- E: coreutils: custom-library-search-path RUNPATH /usr/lib/x86_64-linux-gnu [usr/bin/expr]
- E: coreutils: custom-library-search-path RUNPATH /usr/lib/x86_64-linux-gnu [usr/bin/factor]
dpkg: https://salsa.debian.org/dpkg-team/dpkg/-/pipelines
- Uses a CI pipeline, but does not use Salsa-CI.
We could submit something akin https://salsa.debian.org/apt-team/apt/-/merge_requests/348
But first we need them to allow MRs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075993
- Due to certain problems, MRs can't be allowed in the Salsa repo.
pam: https://salsa.debian.org/vorlon/pam/-/pipelines
- Doesn't use Salsa CI.
Follow-up on https://salsa.debian.org/vorlon/pam/-/merge_requests/14
bzip2: https://salsa.debian.org/debian/bzip2/-/pipelines
- Salsa CI is enabled and green.
debconf: https://salsa.debian.org/pkg-debconf/debconf/-/pipelines
- Uses a customized version of Salsa CI (Add a new job and disable some jobs enabled by default).
tar: https://salsa.debian.org/debian/tar/-/pipelines
- Uses Salsa CI.
- autopkgtest job fails.
acl: https://git.hadrons.org/cgit/debian/pkgs/acl.git
- It doesn't use Salsa.
- TODO: contact the maintainer about using Salsa and Salsa CI
adduser: https://salsa.debian.org/debian/adduser/-/pipelines
- Salsa CI is enabled and green.
perl: https://salsa.debian.org/perl-team/interpreter/perl/-/pipelines
- Salsa CI is enabled but continuously fails at the first job.
- TODO: figure out a way to make it green.
shadow: https://salsa.debian.org/debian/shadow/-/pipelines
- Uses Salsa CI.
- lintian and piuparts emit errors.