#1141907 golang-github-segmentio-encoding fails autopkgtests on some architectures

#1141907#5
Date:
2026-07-12 13:44:55 UTC
From:
To:
Hi,

this package FTBFS during autopkgtests on i386, armhf, and s390x.

I think that i386 and armhf need to be excluded from the architecture
list, because the package Build-Depends on "architecture-is-64-bit",
which cannot be fulfilled on 32 bit architectures.

On s390x, the package depends on "native-architecture-is-amd64 [s390x]",
which cannot be fulfilled, either.

Currently, the autopkgtest failures prevent migration to testing.

Regards,
Tobias

#1141907#10
Date:
2026-07-13 19:36:38 UTC
From:
To:
Hi,
Why would you do this for a source that only builds an arch:all binary?
This is backwards. If you don't want to *test* on non-64 bits, you
should declare so in debian/test/control, ie via the Architectures field
there, which supports negated values
Architecture: !armhf !i386 !s390x

Paul

#1141907#17
Date:
2026-09-07 23:39:02 UTC
From:
To:
tags 1141907 forky sid ftbfs
found 1141907 0.5.4-1
thanks

Hi. This package currently FTBFS on amd64:


=== RUN   TestUnmarshalFuzzBugs/#65
    json_test.go:1321: errors mismatch
    json_test.go:1322: expected: *json.UnmarshalTypeError: json: cannot unmarshal number + into Go struct field .s of type int
    json_test.go:1323: found:    *errors.errorString: json: invalid use of ,string struct tag, trying to unmarshal "+" into int
=== RUN   TestUnmarshalFuzzBugs/#66
--- FAIL: TestUnmarshalFuzzBugs (0.00s)


Because there is usually a high correlation between autopkgtests
failures and build failures, I'm going to assume, for simplicity,
that this is the same bug you reported (but of course I can be wrong,
so if the package builds ok for you, then I can offer a VM to
reproduce, as always).

Thanks.