Re: golang-* not on Salsa
Hi,
On Sat, 6 Sep 2025 Otto Kekäläinen <otto@debian.org> wrote:
> Thanks for this analysis as well!
+1
> 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?
I usually check popcon for this purpose.
> 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?
This would rather find package dependencies, right? I have no idea
about DAK but it could be queried via (build_)depends in UDD.
> 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,
Definitely. I admit last weekend I started with these packages:
udd=> select distinct source, maintainer, vcs_url from sources where release = 'sid' and maintainer like 'pkg-go%' and (vcs_url not like '%salsa%' or vcs_url is null) order by maintainer;
source | maintainer | vcs_url
------------------------------------+-----------------------------------------------------+---------------------------------------------------------------------------------------
golang-coreos-log | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-coreos-log.git/
golang-github-bmizerany-assert | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-bmizerany-assert.git
golang-github-docker-libtrust | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-docker-libtrust.git
golang-github-garyburd-redigo | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-garyburd-redigo.git
golang-github-influxdata-toml | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> |
golang-github-jacobsa-bazilfuse | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-jacobsa-bazilfuse.git
golang-github-jacobsa-fuse | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-jacobsa-fuse.git
golang-github-jacobsa-gcloud | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-jacobsa-gcloud.git
golang-github-jacobsa-oglematchers | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-jacobsa-oglematchers.git
golang-github-jacobsa-oglemock | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-jacobsa-oglemock.git
golang-github-jacobsa-reqtrace | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-jacobsa-reqtrace.git
golang-github-jacobsa-timeutil | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-jacobsa-timeutil.git
golang-github-jacobsa-util | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-jacobsa-util.git
golang-github-samalba-dockerclient | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-samalba-dockerclient.git
golang-github-samuel-go-zookeeper | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-samuel-go-zookeeper.git
golang-github-stevvooe-resumable | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-stevvooe-resumable.git
golang-github-vaughan0-go-ini | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-github-vaughan0-go-ini.git
golang-go-cache | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-go-cache.git
golang-gocolorize | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-gocolorize.git
golang-robfig-config | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-robfig-config.git
golang-sorcix-irc-dev | pkg-go <pkg-go-maintainers@lists.alioth.debian.org> | https://anonscm.debian.org/git/pkg-go/packages/golang-sorcix-irc-dev.git
(21 Zeilen)
and to deal with these easily I added this commit to routine-update:
https://salsa.debian.org/debian/routine-update/-/commit/ee3002f7f684fcf8dc115860d0a10a19a3c9ef44
I also learned that several golang-* packages are featuring Section:
devel instead of golang. This is now fixed (by the Git version of
routine-update!!) as well:
https://salsa.debian.org/debian/routine-update/-/commit/ba06ecc2ce8dec1c0f54b66a57f4dcef4a58a51d
(sorry for the ugly commit which is fixing a bit more than this. :-( )
Given that at DebConf Golang team BoF at DebConf a more extensive Salsa
CI testing was decided (if I understood the video correctly) I took the
freedom to change the debian/gitlab-ci.yml of
golang-github-vmware-photon-controller-go-sdk[1] to use the default
Salsa CI job. I was wondering whether I should implement this change
into routine-update as well. Before I do so I would like to hear
confirmation of the team (and Salsa CI admins) that this is OK in
general. I did it for this specific package since I'm not an
experienced Go packager at all and passing Salsa CI was ensuring me that
an upload should be fine.
> check CI passes, potentially update to a newer version
> etc and only then upload?
In other words: Do what routine-update is doing (which includes
lintian-brush, bumping debhelper compat level, Standards-Version
as well as importing latest upstream), right?
> 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.
Ahhh, I hope I did not created a conflict with some team policy.
I actually intended to start with the wrongly named packages above
since I wanted to something similar as Simon Josefsson.
> 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.
My experience from Perl team is that somehow an "existing" maintainer
should have the ID at Uploaders and the team does whatever is needed to
maintain the package heavily relying on automated packaging updates.
Kind regards
Andreas.
PS: Please CC me if you respond to this thread.
[1] https://salsa.debian.org/go-team/packages/golang-github-vmware-photon-controller-go-sdk/-/commit/a047d2ec3b10c4fff3687d3d885ee6a2d3dfaa53
--
https://fam-tille.de
Reply to: