Hi Felix,
Thanks for trying it out for me.
On Wed, Jan 1, 2020 at 10:36 PM Felix Lechner
<felix.lech...@lease-up.com> wrote:
>
> > E: easygen: statically-linked-binary usr/bin/easygen
>
> This tag is not reproducible in unstable. Build log attached. Closing this
> bug.
>
> Please reopen if a mistake was made.
I'm still seeing that error when I'm building it, but honestly I don't
know what happened at my end, and yours, because I have no idea how it
comes to like this.
Here is what I'm getting now:
$ apt-cache policy lintian
lintian:
Installed: 2.43.0
Candidate: 2.43.0
Version table:
*** 2.43.0 500
500 http://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
$ lintian -EvIL +pedantic ../easygen*_amd64.changes
N: Starting on group easygen/4.1.0-1
N: Unpacking packages in group easygen/4.1.0-1
N: ----
N: Processing changes file easygen
N: (version 4.1.0-1, arch amd64 all) ...
N: ----
N: Processing buildinfo package easygen
N: (version 4.1.0-1, arch all amd64) ...
N: ----
N: Processing binary package easygen
N: (version 4.1.0-1, arch amd64) ...
N: ----
N: Processing binary package golang-github-go-easygen-easygen-dev
N: (version 4.1.0-1, arch all) ...
E: easygen: statically-linked-binary usr/bin/easygen
N: Finished processing group easygen/4.1.0-1
$ file obj-x86_64-linux-gnu/bin/easygen
obj-x86_64-linux-gnu/bin/easygen: ELF 64-bit LSB executable, x86-64,
version 1 (SYSV), statically linked, Go
BuildID=wq5SReT4_T68YpD7UOR9/LOqZugecRUOfQUOmfqkf/uNwyL1fb4NSfnJdS8jK0/sxnLKoUyMvPv0RCeQxvh,
not stripped
Full log available at
http://paste.debian.net/1124280/
including my build test on ffcvt as well.
@Chris,
if Lintian only has visibility against the binary, then maybe the
"Go BuildID" from `file` output can be used as a strong indicator?
