Hi,
Related: https://bugs.debian.org/1146815
Otto's glow/trufflehog look like the XS-Go-Import-Path /vN mismatch
Andrew and Praveen describe — packaging fix.
Santiago's mass FTBFS also includes another mode that is a dh-golang
regression (go.work / replace without go.mod at the target). Same Go
1.27, only dh changes:
golang-goji / golang-github-armon-go-metrics
dh-golang 1.65: PASS
dh-go 1.67: FAIL
So two buckets under "module-aware":
(1) leaf XS-Go-Import-Path /vN — fix debian/control (wiki)
(2) go.work/replace hard-fail — needs fix/rollback in src:dh-golang
Worth checking which bucket a failure is in before mass-filing
leaf bugs. Repro helper: https://salsa.debian.org/-/snippets/871
Hermes
El sáb, 5 sept 2026 a las 16:07, Andrew Lee (<[email protected]>) escribió:
>
> Hi Otto,
>
> Thank you for reporting this.
>
> On Sat, Sep 5, 2026 at 5:36 PM Otto Kekäläinen <[email protected]> wrote:
> > Can someone familiar with this topic explain why these two packages
> > are behaving this way, and what changes I should try or what I should
> > debug to find the root cause?
>
> This happens when XS-Go-Import-Path in debian/control does not match
> the module path declared in upstream's go.mod (such as a missing /v2
> or /v3 major version suffix), dh-go cannot construct the workspace
> directory structure.
>
> We should fix this issue by these steps:
> 1. Align XS-Go-Import-Path from upstream's go.mod.
> 2. Handle Build Dependencies with Versioned Import Path.
> 3. Fork and Upload Versioned Build-deps package.
> 4. Using Versioned Build-deps in debian/control.
> 5. Do Not Delete Legacy Repositories, Simon's zombie cleanup script
> will handle that.
>
> I have updated the Go Team wiki transition FAQ with details on this
> issue and a step-by-step resolution guide:
>
> https://wiki.debian.org/Teams/DebianGoTeam/MigrationFAQ#Align_XS-Go-Import-Path
>
> Please report if any other issue. I will also find the solution and
> update into the wiki page.
>
> Best regards,
> --
> -Andrew
>
