+1 For me the Salsa CI is key to prepare any Go package updates, and the new reverse build feature has saved a lot of painful archive upload mistakes. I don't object to the old Go pipeline, but it never did anything useful for me, and when it fails it doesn't cause any other problem, so I just ignore it. It succeeds even for fatally invalid packaging, such as when pushing some unfinished new package. It could be run in parallel with the Salsa CI pipeline, if someone says they want to keep it. Your pull request could be updated with this small tweak. I think we should use normal debian/salsa-ci.yml naming instead of our (?) Go-team-specific debian/gitlab-ci.yml, but as you say in the pull request, that change can come later. Btw, I think the comment help you add will just go stale over time. How about just make the new Go team debian/salsa-ci.yml (or debian/gitlab-ci.yml as a transition) be the most basic setup: include: - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml I support merging your patch even with the comment. /Simon Otto Kekäläinen <otto@debian.org> writes: > Hi! > > Is the Go team in Debian ready to start using Salsa CI in all new packages > by default? > > I have been proposing this since 2024 [1] and made progress on the topic > step-by-step [2, 3, 4]. A lot of packages have been using > debian/gitlab-ci.yml with the equivalent contents a vanilla salsa-ci.yml > has, and some packages also started using the filename salsa-ci.yml. Some > packages have been running both old and new CI in series, and some have > used both old and new filename, proving that gradual migration is seamless. > There has been zero regressions and no downsides of using Salsa CI has > surfaced. > > In September 2025 we also got the ability to test reverse dependencies with > ratt integrated directly into Salsa CI [5], which people hopefully use more > and more in the future to prove new library versions are compatible enough > to be uploaded. > > The next step now in January 2026 is to have the vanilla Salsa CI contents > as the default contents in new packages. > > If you agree, please vote by doing +1 or Approve on > https://github.com/Debian/dh-make-golang/pull/279 > > After the above, the last and final step in this transition would be to > make debian/salsa-ci.yml the default CI path for all new Go team package > repositories. That can be addressed later, potentially utilizing the new > Flight Deck service. However, merging #279 is the immediate priority. > > Thanks! > > [1] https://lists.debian.org/debian-go/2024/09/msg00013.html > [2] https://lists.debian.org/debian-go/2024/10/msg00064.html > [3] https://lists.debian.org/debian-go/2024/12/msg00021.html > [4] https://lists.debian.org/debian-go/2025/01/msg00005.html > [5] https://lists.debian.org/debian-go/2025/09/msg00074.html
Attachment:
signature.asc
Description: PGP signature