Hi Nilesh, I'd keep that tag for now (or even strengthen it). With module-aware builds, XS-Go-Import-Path ≠ go.mod is exactly the /vN FTBFS class. Cleanup only makes sense once XS-Go-Import-Path itself is retired.
Hermes El sáb, 5 sept 2026 a las 17:48, Nilesh Patra (<[email protected]>) escribió: > > > > On 06/09/26 3:12 am, Nilesh Patra wrote: > > On 06/09/26 1:36 am, Andrew Lee wrote: > >> 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. > > Once this transition completes, do we still need this lintian tag? > > > > https://lintian.debian.org/tags/xs-go-import-path-differs-from-module-path.html > > > > If not, it'd be best to clean this up and save compute. Would be nice if > > someone > > opens a bug report on lintian asking to clean this (I am not keeping a > > track of > > all conversations on the mailing list). > > Same question also for > > https://lintian.debian.org/tags/missing-xs-go-import-path-for-golang-package.html >
