Re: Should we delete pkg-go-tools, provisioning, migrate-pkg-go-to-salsa etc?
Hi!
I am reviewing this thread from May and July.
I have now marked https://salsa.debian.org/go-team/stapelbergtest for
deletion, and archived
https://salsa.debian.org/go-team/migrate-pkg-go-to-salsa, as there was
enough consensus on that and many many months passed without anyone
raising objections.
Looking at https://salsa.debian.org/go-team/infra/pkg-go-tools/-/commits
and https://salsa.debian.org/go-team/infra/provisioning/-/commits,
they haven't had "real" and "tanglible" improvements since 2021 and
2022 respectively. Aloïs, what is your current plan about these? If
you don't continue with these, have you had discussions with someone
else who would like to take over and maintain these?
On Wed, 9 Jul 2025 at 12:37, Aloïs Micard <creekorful@debian.org> wrote:
>
> Hello,
>
> On 09/07/2025 19:23, Otto Kekäläinen wrote:
>
> Hi!
>
> I am reviving this thread from May.
>
> Nobody expressed anything about these repositories, so I plan to mark
> them as archived in a couple of weeks unless anyone objects:
>
> https://salsa.debian.org/go-team/migrate-pkg-go-to-salsa
> https://salsa.debian.org/go-team/stapelbergtest
>
> You can go ahead with those repositories, they are useless nowadays.
>
>
> The state of these is documented in the README but as the CI seems to
> be broken (CI always passes and never detects any real issues) we
> might want to deprecate these in coming years:
> https://salsa.debian.org/go-team/infra/pkg-go-tools
> https://salsa.debian.org/go-team/infra/provisioning
>
>
> This could be done too but keep in mind that `create-salsa-project` command defined in dh-make-golang and gophian will not work anymore.
>
> Not necessary a problem but a migration/alternative need to be in place. I personally don't see the benefits of dropping it.
>
> See: https://salsa.debian.org/go-team/infra/pkg-go-tools/-/blob/master/README.md?ref_type=heads#pgt-api-server
>
> Cheers,
>
>
>
>
> On Mon, 28 Apr 2025 at 20:50, Otto Kekäläinen <otto@debian.org> wrote:
> >
> > Hi,
> >
> > What is the current maintenance plan for these?
> >
> > https://salsa.debian.org/go-team/infra/pkg-go-tools
> > https://salsa.debian.org/go-team/infra/provisioning
> > https://salsa.debian.org/go-team/migrate-pkg-go-to-salsa
> > https://salsa.debian.org/go-team/stapelbergtest
> >
> > Should we plan to stop using them and gracefully deprecate them, mark
> > them archived or delete them?
> >
> > I have not seen the CI job test_the_archive be useful in any of the
> > packages I worked on. I am not fully sure if I even understand what
> > the intent of that CI job, as it is doing only a source package build
> > and otherwise testing other packages than what actually triggered the
> > CI run.
> >
> > See e.g. https://salsa.debian.org/go-team/packages/usql/-/jobs/7283517
> > failing on various go commands but job passes anyway:
> > go: errors parsing go.mod:
> > /builds/go-team/packages/usql/go.mod:5: unknown directive: toolchain
> >
> > The only way to get the test_the_archive job to fail is to give inputs
> > that don't even produce a source package, e.g. vs
> > https://salsa.debian.org/go-team/packages/usql/-/jobs/7283480
> >
> >
> > I am sure these Go team infra pieces were useful 2-3 years ago, but
> > going forward, does it makes sense to spend energy on maintaining
> > these?
Reply to: