[pkg-go] Bug#1105153: gocryptfs: Salsa CI is failing

[Otto Kekäläinen]

Checking:

- https://tracker.debian.org/pkg/gocryptfs says 2.5.1-2 was uploaded
today, i386 build passed at
https://buildd.debian.org/status/package.php?p=gocryptfs
- https://salsa.debian.org/go-team/packages/gocryptfs has 2.5.1-2 as
latest commit
- repo user branch 'master' and hosts only the debian/ subdirectory
- https://salsa.debian.org/go-team/packages/gocryptfs/-/blob/master/debian/gbp.conf
is forbidding use of pristine-tar, yet not using upstream tags either,
so no security features in use
- https://salsa.debian.org/go-team/packages/gocryptfs/-/pipelines/864484
is not running Salsa CI
- custom go test failing on:

gbp:info: Tarballs 'gocryptfs_2.5.1.orig.tar.gz' not found at '/nonexistent'
gbp:error: upstream/2.5.1 is not a valid trees

If you adopt a sensible git structure and have gbp.conf configured, I
can take a look. Otherwise I am just wasting effort debugging someones
custom structures.

Here is a general primer into what the various branches in Debian /
git-buildpackage are and what they are used for:
https://optimizedbyotto.com/post/debian-source-package-git/

If you want to help me with Salsa CI, the pipeline should also adopt
Salsa CI first. This is the CI file the repository is currently
configured to use:
https://salsa.debian.org/go-team/packages/gocryptfs/-/blob/master/debian/gitlab-ci.yml

I would recommend going forward that you push to Salsa first, wait for
CI to pass, and if it didn't, re-iterate until it passes.