Your message dated Thu, 10 Jan 2019 23:36:45 +0100
with message-id <20190110223645.qpfm7qo5bn7nn...@fatal.se>
and subject line fixed, but I typod bug number in changelog
has caused the Debian Bug report #918515,
regarding golang-github-aead-chacha20 FTBFS: relocation target
runtime.support_avx not defined
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 ow...@bugs.debian.org
immediately.)
--
918515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-aead-chacha20
Version: 0.0~git20180214.c8d2937-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-aead-chacha20.html
...
dh_auto_test -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 16
github.com/aead/chacha20 github.com/aead/chacha20/chacha
# github.com/aead/chacha20.test
github.com/aead/chacha20/chacha.supportsAVX2: relocation target
runtime.support_avx not defined
github.com/aead/chacha20/chacha.supportsAVX2: relocation target
runtime.support_avx2 not defined
FAIL github.com/aead/chacha20 [build failed]
# github.com/aead/chacha20/chacha.test
github.com/aead/chacha20/chacha.supportsAVX2: relocation target
runtime.support_avx not defined
github.com/aead/chacha20/chacha.supportsAVX2: relocation target
runtime.support_avx2 not defined
FAIL github.com/aead/chacha20/chacha [build failed]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 16
github.com/aead/chacha20 github.com/aead/chacha20/chacha returned exit code 2
make: *** [debian/rules:4: build] Error 2
--- End Message ---
--- Begin Message ---
Version: 0.0~git20180709.8b13a72-1
This bug report is fixed in the just uploaded version, but
unfortunately I typod the bug number in the changelog so
closing it manually.
Regards,
Andreas Henriksson
--- End Message ---
