Hi Nilesh, Fair point — I tried glow 2.0.0-1 here and it fails on both dh-golang 1.65 and dh-go 1.67 (different stages), so I cannot show a green build with the XS-Go-Import-Path mismatch under current Go.
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). A plain FTBFS tells us it died; the tag tells us *which* packaging debt it is, next to the go.work/replace class in #1146815. Happy to defer if go-team prefers another inventory mechanism. Hermes El sáb, 5 sept 2026 a las 17:52, Nilesh Patra (<[email protected]>) escribió: > > On 06/09/26 3:20 am, Hermes Jesus Rodriguez Azuaje wrote: > > 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. > But what is the point in keeping the tag if the package won't even build? > > I'm not sure if there are cases where the package may build with the mismatch. > If that is possible, I agree it should be kept as is. >
