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
