Your message dated Sun, 13 Jan 2019 10:16:52 +0100
with message-id <20190113091652.lv3cqhxrqpwnc...@fatal.se>
and subject line Re: fixes in dependencies....
has caused the Debian Bug report #918629,
regarding dnscrypt-proxy FTBFS with Go 1.11
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.)
--
918629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dnscrypt-proxy
Version: 2.0.19+ds1-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dnscrypt-proxy.html
...
github.com/jedisct1/dnscrypt-proxy/dnscrypt-proxy
# github.com/jedisct1/dnscrypt-proxy/dnscrypt-proxy
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
github.com/aead/poly1305.supportsAVX2: relocation target runtime.support_avx2
not defined
dh_auto_build: cd obj-x86_64-linux-gnu && go install
-gcflags=all=\"-trimpath=/build/1st/dnscrypt-proxy-2.0.19\+ds1/obj-x86_64-linux-gnu/src\"
-asmflags=all=\"-trimpath=/build/1st/dnscrypt-proxy-2.0.19\+ds1/obj-x86_64-linux-gnu/src\"
-v -p 15 github.com/jedisct1/dnscrypt-proxy/dnscrypt-proxy returned exit code 2
make: *** [debian/rules:12: build] Error 2
--- End Message ---
--- Begin Message ---
On Thu, Jan 10, 2019 at 11:29:51PM +0100, Andreas Henriksson wrote:
> block -1 by 918514 918515
> thanks
>
> Hopefully this ftbfs should vanish with the dependencies being fixed,
> see:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=918514
> https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=918515
I triggered a rebuild on reproducible-builds amd64 yesterday and indeed
it went from 'not building' to 'not reproducible'. (See also the
arm64 build which was already done recently and also confirms there's
no longer a FTBFS problem.)
I'm thus taking the liberty to close this bug report now as it wasn't
really a bug in dnscrypt-proxy itself.
Regards,
Andreas Henriksson
--- End Message ---
