tags 911864 + pending
thanks
Hi Jeffrey,
> 8) debuild -uc -us -b
^^
Ahh, so in this case Lintian does not access to the source package
and thus cannot determine the build-depends. Fixed in Git, pending
upload:
I just spun up a new amd64 sid vm and replicated.
1) install buster
2) change /etc/apt/sources.list to sid
3) apt-get update, apt-get ugprade, apt-get dist-upgrade
4) reboot
5) apt-get install (tor, git, aptitude) dh-golang, gccgo golang-go
golang-github-mattn-go-colorable-dev
Jeffrey,
> I had tried with golang-go, with gcc-go, same thing happens. I haven't
> tried golang-any though.
I just tried building package after uncommenting out "golang-go"
from the Build-Depends.
This silenced the warning for me, so I suggest there is something
amiss with your testcase.
I had tried with golang-go, with gcc-go, same thing happens. I haven't
tried golang-any though.
E: golang-notabug-themusicgod1-panicparse-dev: statically-linked-binary
usr/bin/panic
Trying with golang-any...and the same thing happens.
On Fri, 26 Oct 2018 at 00:28, Chris Lamb wrote:
> tags
tags 911864 + moreinfo
thanks
Hi Jeff,
> According to #718404, golang packages aren't supposed to give an error
> of statically-linked-binary because all go language packages are
> apparently statically linked.
lintian uses whether a package build-depends against golang-go or
golang-any to
Package: lintian
Version: 2.5.110
Severity: normal
Dear Maintainer,
According to #718404, golang packages aren't supposed to give an error of
statically-linked-binary because
all go language packages are apparently statically linked. And yet attempting
to build
6 matches
Mail list logo
