Hi,
I have not been able to reproduce any build failure with the package as
it currently is in salsa. I've successfully built across unstable,
testing, and stable with sbuild using up-to-date chroots.
With that said, I _think_ there might be some confusion in the
Build-Depends that results in different packages being resolved during
build. The control file lists
golang-github-cenkalti-backoff-v4-dev | golang-github-cenkalti-backoff-dev
but depending on which distribution is being built against, the package
golang-github-cenkalti-backoff-dev can refer to different major versions
(summarized below).
- golang-github-cenkalti-backoff-dev
- oldstable 4.1.3-1 /usr/share/gocode/src/github.com/cenkalti/backoff/
- stable 4.3.0-1 /usr/share/gocode/src/github.com/cenkalti/backoff/
- testing 5.0.3-3 /usr/share/gocode/src/github.com/cenkalti/backoff/
- golang-github-cenkalti-backoff-v4-dev
- testing 4.3.0-3 /usr/share/gocode/src/github.com/cenkalti/backoff/v4/
For unstable/testing, the correct dependency is
golang-github-cenkalti-backoff-v4-dev with the patch to include the v4
path component. For older distributions the correct dependency is
golang-github-cenkalti-backoff-dev without the patch. I wonder if adding
a version constraint (e.g., `(<< 5.0.0)`) to the Build-Depends is
needed? Additionally, the backoff-v4 patch needs to be omitted when
building for older distributions.
-- Bradford
