Re: scripts for DEP-14 migration
Hi!
I am all in favor of these changes as I suggested mostly the same a
year ago. I just hope we can do the migration in a slow and controlled
way, and upgrade all tools and currently outdated docs in the process.
> On 26/08/25 at 10:05 +0200, Simon Josefsson wrote:
> > Perhaps the debian/salsa-ci.yml should contain something like this:
> >
> > include:
> > - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml
> > - https://salsa.debian.org/go-team/infra/pkg-go-tools/-/raw/master/pipeline/team.yml
>
> You could even set it to:
>
> ----
> include:
> - https://salsa.debian.org/go-team/infra/pkg-go-tools/-/raw/master/pipeline/team.yml
> ----
>
> and add the include of
> https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml
> in pkg-go-tools/pipeline/team.yaml
>
> (see "management of debian/salsa-ci.yml" thread in
> https://lists.debian.org/debian-ruby/2025/08/threads.html)
On the Go team list multiple people have raised a couple of times that
the custom Go CI job actually does not test things that are useful for
the specific package it runs for. My proposal is to fully replace it
with vanilla salsa-ci.yml, and start out by having both
debian/gitlab-ci.yml and debian/salsa-ci.yml in parallel so that
project settings can be migrated over time with both new and old
working in parallel:
https://github.com/Debian/dh-make-golang/pull/279.
In general I'd suggest we
1. first make sure dh-make-golang creates *new* projects with optimal settings
2. then convert projects semi-automated by only one at a time when a
human is uploading and can check everything went fine
3. only finally after 6-12 months seeing all is good with new and
converted projects do a mass migration for the remaining ones
For reference previous threads on the topic:
* https://lists.debian.org/debian-go/2024/12/msg00021.html
* https://lists.debian.org/debian-go/2025/01/msg00045.html
Reply to: