* Michael Prokop [Thu Nov 12, 2020 at 07:55:47AM +0100]:
> Package: golang-github-gomodule-redigo-dev
> Version: 2.0.0-1
> Severity: normal

> while it looks like version 2.0.0-1 of the
> golang-github-gomodule-redigo-dev package matches the latest
> upstream version, this doesn't seem to really match reality.

> Looking at https://github.com/gomodule/redigo/tags we have the
> following versions/tags with their corresponding "release date" next
> them:

> v1.8.2 on 2020-06-08
> v1.8.1 on 2020-05-06
> v1.8.0 on 2020-04-30
> v1.7.2 on 2020-04-30
> v1.7.1 on 2020-04-30
> v1.7.0 on 2018-12-13
> v2.0.0 on 2018-03-14(!)

> So v2.0.0 is actually the oldest version, while upstream's
> newest version as of today is v1.8.2, due to a version number
> downgrade to 1.7.0 after the 2.0.0 release back in 2018).

> We can either only introduce an epoch version :-/ - or hope for
> upstream raising their version number, I tried to bring this up at
> upstream at https://github.com/gomodule/redigo/issues/532

So sadly my request to fix the version situation from upstream side
was closed (see https://github.com/gomodule/redigo/issues/532),
so I'm afraid we have to introduce an epoch version to handle this. :(

Dmitry, is there any chance you could take care this?

regards
-mika-

Attachment: signature.asc
Description: Digital signature

Reply via email to