[pkg-golang-devel] Epoch version for golang-github-gomodule-redigo-dev?

[Michael Prokop]

Hi,

we have a rather unfortunate situation with the
golang-github-gomodule-redigo-dev package, see #974550 for the
details.

tl;dr: upstream released v2.0.0 on 2018-03-14, though went downwards
with version numbers afterwards and we're at v1.8.3 for the latest
upstream release now. In Debian we currently have v2.0.0 in
buster/testing/unstable.

It looks like upstream isn't willing to raise the version number
(see https://github.com/gomodule/redigo/issues/532, and a somewhat
related discussion took place also in
https://github.com/gomodule/redigo/issues/366), so if we want to fix
the situation for bullseye, we need a workaround/solution soonish.

Since the problem exists due to the way go module versioning works,
it might make sense to discuss, how to handle it a) now for
golang-github-gomodule-redigo-dev, but also b) apply the same
decision whenever the issue comes up again?

The situation is related to the fact how go module versioning works:

* `go get github.com/gomodule/redigo/redis` currently points at v1.8.3
* https://pkg.go.dev/github.com/gomodule/redigo/redis?tab=versions
  says v1, both for v1.8.3 but also v2.0.0+incompatible

AFAICS we could:

1) use 2.0.0+really1.8.3 pattern for our Debian package version
2) introduce an epoch
3) any further trick/workaround?

Thoughts?

Thanks to Clément Hermann, Tianon Gravi and Shengjing Zhu for their
feedback on #debian-golang.

regards
-mika-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-golang-devel/attachments/20201126/db9479e6/attachment.sig>