Marcos Talau <[email protected]> writes: > Hi there! > > [I added Andrew Lee to the conversation.] > > During last week's DebConf I participated in a Go sprint, and one of the tasks > assigned was to add this file to several packages [1] and then adjust the CI > configuration. The first part I did was add this file; the second step I was > going to do was adjust the CI configuration.
A debian/salsa-ci.yml is not required for that. You could also have mass-updated the GitLab CI/CD Configuration File to use the value 'https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml' for any package still using the (IMHO useless) 'debian/gitlab-ci.yml' setting. Be sure to not update any package using an existing debian/salsa-ci.yml file. Alternatively, if somebody object to the above, create a personal Salsa fork of each project, setting the CI/CD configuration file for that personal fork only. This is what I do. /Simon > I apologize if this was incorrect. > > [1] https://wiki.debian.org/DebConf/26/Sprints/DebianGoTeam/GoModBuilds > > > Best Regards, > mt > > On Sat, Aug 01, 2026 at 09:44:58AM +0300, Otto Kekäläinen wrote: >> Hi Marcos, >> >> Can you please stop doing bulk commits? >> >> Adding this file to repos do not create any value alone, only confusion, >> clutter and cleanup work for others. >> >> If you want to help, fix *one package at a time* and show ownership of your >> changes by making sure that packages your touch are actually fixed. >> >> On Sat., Aug. 1, 2026, 09:25 Nick Morrott, <[email protected]> >> wrote: >> >> > Whilst working on updating the build-deps of packages affected by the >> > move of tslocum/cbind (and cview) to codeberg and the renamed binary >> > packages uploaded as a result, I have noticed the recent mass commit >> > of d/salsa-ci-yml files by Marcos Talau (talau) into these repos (and, >> > possibly, a few hundred others). >> > >> > E.g.: >> > >> > https://salsa.debian.org/go-team/packages/amfora/-/tree/master/debian >> > https://salsa.debian.org/go-team/packages/gomuks/-/tree/debian/sid/debian >> > https://salsa.debian.org/go-team/packages/fq/-/tree/debian/sid/debian >> > >> > https://salsa.debian.org/go-team/packages/golang-github-containerd-nydus-snapshotter/-/tree/debian/sid/debian >> > >> > https://salsa.debian.org/go-team/packages/golang-github-awslabs-soci-snapshotter/-/tree/debian/sid/debian >> > https://salsa.debian.org/go-team/packages/lf/-/tree/debian/master/debian >> > >> > >From the small sample of maybe half a dozen projects that I quickly >> > checked (above), these repos: >> > >> > *) already have an existing d/gitlab-ci.yml file present >> > *) already have Salsa CI configured to use this d/gitlab-ci.yml file >> > >> > The newly committed d/salsa-ci.yml files are therefore not providing >> > anything of value that I can see. >> > >> > Is there a specific reason for this mass commit of additional CI >> > files? Is it going to be followed by a mass update of repo settings to >> > switch from d/gitlab-ci to d/salsa-ci config files? >> > >> > Cheers, >> > Nick >> > >> > >
signature.asc
Description: PGP signature
