Your message dated Sat, 28 Jan 2023 16:07:44 +0100 with message-id <Y9U6QNND6Ej83/I/@angband.pl> and subject line not a bug in bullseye has caused the Debian Bug report #1027370, regarding golang-github-powerman-check: FTBFS in bullseye (missing build-depends on tzdata) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1027370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027370 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: src:golang-github-powerman-check Version: 1.2.1-2 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: -------------------------------------------------------------------------------- [...] debian/rules binary-indep dh binary-indep --builddirectory=_build --buildsystem=golang --with=golang dh_update_autotools_config -i -O--builddirectory=_build -O--buildsystem=golang dh_autoreconf -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_configure -i -O--builddirectory=_build -O--buildsystem=golang dh_auto_build -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go install -trimpath -v -p 2 github.com/powerman/check internal/unsafeheader internal/cpu runtime/internal/atomic internal/bytealg runtime/internal/sys runtime/internal/math internal/race runtime sync/atomic unicode unicode/utf8 encoding math/bits math internal/testlog unicode/utf16 golang.org/x/sys/internal/unsafeheader internal/reflectlite sync errors sort io strconv bytes internal/oserror syscall reflect internal/syscall/unix time encoding/binary internal/fmtsort internal/poll encoding/base64 internal/syscall/execenv strings os regexp/syntax fmt regexp encoding/json flag encoding/hex github.com/davecgh/go-spew/spew path github.com/pkg/errors bufio github.com/smartystreets/goconvey/convey/gotest github.com/smartystreets/goconvey/convey/reporting github.com/pmezard/go-difflib/difflib path/filepath golang.org/x/sys/unix io/ioutil runtime/debug context runtime/trace testing github.com/powerman/check dh_auto_test -i -O--builddirectory=_build -O--buildsystem=golang cd _build && go test -vet=off -v -p 2 github.com/powerman/check panic: time: missing Location in call to Time.In goroutine 1 [running]: time.Time.In(0xc0ac7376985035d0, 0xa8c01, 0x715b20, 0x0, 0x6f93a0, 0xc0000d1f18, 0x1) /usr/lib/go-1.15/src/time/time.go:1099 +0xb2 github.com/powerman/check_test.init() /<<PKGBUILDDIR>>/_build/src/github.com/powerman/check/check_test.go:150 +0x236 FAIL github.com/powerman/check 0.007s FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 2 github.com/powerman/check returned exit code 1 make: *** [debian/rules:4: binary-indep] Error 25 dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit status 2 -------------------------------------------------------------------------------- (The above is just how the build ends and not necessarily the most relevant part) Note: I'm using the "patch" tag because there is an obvious fix (indicated in the subject). About the archive rebuild: The build was made using virtual machines from Hetzner, with enough memory, enough disk, and either one or two CPUs, using a reduced chroot with only build-essential packages (plus debhelper). If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
--- End Message ---
--- Begin Message ---Hi! This MBF has been done _contrary_ to multiple discussions on debian-devel and elsewhere. While the wording of the Policy might be a bit unclear (even though everyone but Santiago seems to agree with the other interpretation), beyond any doubt this is not a material for a _stable_ update. A build failure in a supported environment is worth fixing, failing to build when explicitly declared "totally broken" by the Policy (§2.5) s not. I'm thus closing. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Let's make a Debian conference in Yalta, Ukraine. ⢿⡄⠘⠷⠚⠋⠀ ⠈⠳⣄⠀⠀⠀⠀
--- End Message ---
