On 9/1/24 6:22 AM, Philip Hands wrote:
If you look at the repo on Salsa, and find:
Settings > CI/CD > General Pipelines > CI/CD configuration file
you'll see it's set to:
recipes/debian.yml@salsa-ci-team/pipeline
which is how the pipeline gets it's configuration.
The documentation is here:
https://salsa.debian.org/salsa-ci-team/pipeline/
Even for the simplest configurations, I've concluded that it's better to
use the approach where one creates a `debian/salsa-ci.yml` file, and
points to it in the above mentioned setting.
I would be delighted to make this change, but I cannot, because for
whatever reason Russ Allberry opted to make me a Developer on the
project instead of a Maintainer so I can't see or modify its settings.
(This is also why I was unable to figure out where the pipeline setting
was coming from: as a Developer, I can't see it.)
Over to you, Russ. ;-)
In any case, thank you to everyone who responded to my request for
assistance. I was able to fix this Salsa pipeline problem by adding
pybuild-plugin-pyproject to Build-Depends as suggested by Colin Watson.
However, the pipeline is still failing, now in reprotest. For example
<https://salsa.debian.org/debian/apt-listchanges/-/jobs/6215633#L1650>.
Perhaps this is because I haven't yet finalized the changelog for the
upcoming release so the trailer line is badly formatted. :shrug:
jik
