Am 08.09.26 um 19:42 schrieb Andrew Lee:
> Hi Nilesh, (cc'ed Toddy)
> 
> On Tue, Sep 8, 2026 at 4:22 PM Nilesh Patra <[email protected]> wrote:
>> Lintian maintainer here.
>>
>> Is it not possible to have this check inside dh-go and have the package not
>> build if this happens? You could go ahead and ask lucas/sanvila for archive
>> rebuilds to figure out which packages need fixing.
>>
>> There are already 2 tags which will be no longer useful after the transition
>>
>> missing-xs-go-import-path-for-golang-package
>> xs-go-import-path-differs-from-module-path
>>
>> I feel adding one more tag which will again go away after the transition is
>> not a good use of my time.
>> If it is not possible to have it via dh-go and there is another reason to
>> add it in lintian, please let me know. Otherwise, please close this bug.
> 
> Good point. I'm cc to dh-go maintainer Toddy.
> 
> @Tobias, would that be make sense to implete such package name check
> in dh-go and prevent people builds the package?
> 
> Or it's better to warning in lintian instead blcok the builds in dh-go
> for special case?

Hi Andrew and Nilesh,

first of all, thanks a lot to Nilesh for implementing those two tags, I
consider them hugely useful right now. Especially
xs-go-import-path-differs-from-module-path, which flags ~240 packages we
need to work on.

However, when this transition is over, both tags should have close to
zero packages which trigger them. I think Nilesh is right here.

Regarding the proposed new tag in this bug report, I also think it makes
sense to implement a check in dh-go. However, I'm not sure we want to
have build failures right now if the binary package name does not
include the correct version suffix.

I agree it's sensible in the long run. But right now, we already have
loads of packages which FTBFS with the new tooling, even without this
check. Shouldn't we concentrate our efforts in fixing the build failures
first?

If most packages build with dh-go, we can reconsider to implement a new
check for the binary package name.

Regards,
Tobias

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to