Re: go-tuf versioning (was: Re: golang-github-jackc-pgx v4->v5?)

[Nicolas Peugnet <nicolas@club1.fr>]

7 janv. 2025 17:16:14 Simon Josefsson <simon@josefsson.org>:
> I'm open to ideas on how to improve things here, but the situation is
> messy, and hopefully also transitory.
>
> Having two source packages would not help: the problem is that upstream
> has file conflicts, so if there are two Debian source packages with one
> binary Debian package each, they would put files at the same location 
> in
> /usr and would thus have to Conflict.  But there are packages (e.g.,
> cosign) that ultimately Build-Depends on both, so both has to be
> installed at the same time.

It seems to me the reason you have a conflict in installed source files 
it because you didn't update the XS-Go-Import-Path with the /v2 suffix in 
version 2 of this package. As dh_golang installs the source package in 
/usr/share/gocode/src/$DH_GOPKG, and as DH_GOPKG
uses the first value of XS-Go-Import-Path, it would allow to have both 
installed at the same time. In my understanding this is the very reason 
why Go forced the import path to change for major versions.

So if I understood correctly the problem here, having v2 in the /v2 
subdirectory should allow to reintroduce a v0 in the parent one.


--
Nicolas Peugnet