Re: golang-* not on Salsa

[Otto Kekäläinen <otto@debian.org>]

Hi!

> I can think of at least two ways to go about this:
>
> 1) Work manually step by step on each package making all relevant
> updates, or
>
> 2) Write scripts that works on all packages below, which could work like
> this:

Thanks for this analysis as well! Before we go and do a bunch of
updates for the sake of updates, do we have some tooling to check if a
package is actually needed anymore at all?

Could you run some dak spell on all golang-*-dev packages and see
which ones have no consumers, and we could then perhaps just remove
them from Debian as obsolete?

And for the remaining ones, we should probably not do an upload to
Debian with only one line in debian/control changed, but perhaps run
lintian-brush, check CI passes, potentially update to a newer version
etc and only then upload? This is an interesting discussion tangenting
what "team maintained" even means. I don't think any random Go package
is actually maintained despite the team, as we haven't done any
team-wide package updates to my knowledge. We should perhaps check
first which of the current Uploaders are actually active and decide
what "team maintenance" means for packages that are in Go team but
does not have an active uploader.