Hi Nilesh,

Agreed — my tracking argument is for *during* the transition.

Once it completes: if XS-Go-Import-Path remains a packaging
field, I'd keep
xs-go-import-path-differs-from-module-path as a cheap
regression guard. If the field is retired (dh reads go.mod
only), both that and
missing-xs-go-import-path-for-golang-package can go.

Happy to follow whatever go-team decides for the field's
future.

Hermes

El sáb, 5 sept 2026 a las 18:33, Nilesh Patra (<[email protected]>) escribió:
>
>
>
> On 06/09/26 3:50 am, Hermes Jesus Rodriguez Azuaje wrote:
> > I still see value in keeping the tag as *tracking* during the
> > transition: it inventories the /vN mismatch class across the
> > archive (source upload / Salsa / mass-QA).
>
> Yes, sure. My initial question therefore was
>
> *Once this transition completes*, do we still need this lintian tag?
>
> This question is for "xs-go-import-path-differs-from-module-path"
> and "missing-xs-go-import-path-for-golang-package"
>

Reply via email to