<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 02/23/2018 05:10 PM, Michael
      Stapelberg wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CANnVG6kHYf6YEDYWfXGQ2wePUwX5p=3K=hzERR971Zq_1R7D-w@mail.gmail.com">
      <div dir="ltr">I can’t have a look at the individual packages
        right now</div>
    </blockquote>
    <br>
    No rush !<br>
    <br>
    <blockquote type="cite"
cite="mid:CANnVG6kHYf6YEDYWfXGQ2wePUwX5p=3K=hzERR971Zq_1R7D-w@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              #### containerd<br>
              <<a
                href="https://salsa.debian.org/elboulangero-guest/containerd"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://salsa.debian.org/<wbr>elboulangero-guest/containerd</a>><br>
              - There's a lintian warning about
              package-contains-vcs-control-<wbr>file, but<br>
              until<br>
                now I didn't find the right way to remove a file from
              installation. I<br>
              guess<br>
                `override_dh_auto_install` is the way to go. Any hint
              welcome here.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Which file specifically is affected? The Files-Excluded
              directive in debian/copyright is a good way to exclude
              files.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    There's a `docs/.gitignore`, it's in a subdirectory. Files-Excluded
    will remove it from the orig tarball, right ? Is it really suitable
    here ?<br>
    <br>
    For the moment the only package in which I exclude a file from
    installation is done this way:<br>
    <br>
    override_dh_auto_install:<br>
        dh_auto_install<br>
        find $(CURDIR)/debian -name '.tool' -type d -prune -exec rm -r
    '{}' +<br>
    <br>
    Not really elegant, and it took me two hours to come up with that,
    after trying and failing every other way possible...<br>
    <br>
    <blockquote type="cite"
cite="mid:CANnVG6kHYf6YEDYWfXGQ2wePUwX5p=3K=hzERR971Zq_1R7D-w@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div> <br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <br>
              #### golang-github-containerd-btrfs<br>
              <<a
href="https://salsa.debian.org/elboulangero-guest/golang-github-containerd-btrfs"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://salsa.debian.org/<wbr>elboulangero-guest/golang-<wbr>github-containerd-btrfs</a>><br>
              <<a
                href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890989"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://bugs.debian.org/cgi-<wbr>bin/bugreport.cgi?bug=890989</a>><br>
              - I disabled the test to avoid installing a btrfs-test
              binary, plus I think the<br>
                test failed for some reason, I'm not sure to remember
              though...<br>
            </blockquote>
            <div><br>
            </div>
            <div>To avoid installing a binary, can you use
              the DH_GOLANG_EXCLUDES option please? See <a
href="https://manpages.debian.org/testing/dh-golang/Debian::Debhelper::Buildsystem::golang.3pm.en.html"
                moz-do-not-send="true">https://manpages.debian.org/testing/dh-golang/Debian::Debhelper::Buildsystem::golang.3pm.en.html</a></div>
            <div><br>
            </div>
            <div>Also, please add a comment stating why precisely the
              tests are disabled, and what needs to change so that we
              can re-enable them.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Ok I'll try harder :)<br>
    <br>
    I noticed that DH_GOLANG_EXCLUDES will not save me from a test which
    fails though. For example, when I was working with
    containerd/cgroups, the test commmand invoked by dh looks like that:<br>
    <br>
        go test -vet=off -v -p 8 github.com/containerd/cgroups<br>
    <br>
    DH_GOLANG_EXCLUDES is matched against github.com/containerd/cgroups,
    so if it contains a file inside the cgroups directory, it's not
    excluded from the files being tested.<br>
    <br>
    It means that if I want to prevent a file from the test, I still
    need to patch it with `// +build ignore`, if I understand properly.<br>
    <br>
    <blockquote type="cite"
cite="mid:CANnVG6kHYf6YEDYWfXGQ2wePUwX5p=3K=hzERR971Zq_1R7D-w@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <br>
              I see that most binaries come with the lintian warning<br>
              `statically-linked-binary`, I guess it's just the way it
              works in the<br>
              go world. Should I just add a lintian override ?<br>
            </blockquote>
            <div><br>
            </div>
            <div>lintian does not emit the statically-linked-binary tag
              for Go packages. Can you point me to a specific example
              where you see it please?</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Yep, easy.<br>
    <br>
      apt-get download gogoprotobuf<br>
      lintian gogoprotobuf_*_amd64.deb<br>
    <br>
    Is this warning related to the field `Built-Using:
    ${misc:Built-Using}` for binary packages ? After reading the Debian
    Policy Manual, I seem to understand that this field is needed for go
    binary packages, am I correct ?<br>
    <br>
    However even with this field, there is still the warning in the
    `containerd` binary package that I built here, but only for *some*
    of the binaries in the package, not all of them.<br>
    <br>
    <blockquote type="cite"
cite="mid:CANnVG6kHYf6YEDYWfXGQ2wePUwX5p=3K=hzERR971Zq_1R7D-w@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <br>
              In the `-dev` packages, is `${shlibs:Depends}` needed ?
              During the builds<br>
              I see `unknown substitution variable ${shlibs:Depends}`
              passing by.<br>
            </blockquote>
            <div><br>
            </div>
            <div>The messages implies it’s not required. I’m not
              entirely sure, but would suggest removing it for now.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Ok. I think it should be also changed in dh-make-golang, should I
    look there and issue a PR, or do you prefer not to touch it for now
    ?<br>
    <br>
    <blockquote type="cite"
cite="mid:CANnVG6kHYf6YEDYWfXGQ2wePUwX5p=3K=hzERR971Zq_1R7D-w@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <br>
              In the `-dev` packages, do we really need to copy-paste
              all the<br>
              dependencies from the source package ?<br>
            </blockquote>
            <div><br>
            </div>
            <div>Yes. They differ in some cases, for example when code
              generation needs more dependencies than the actual
              compilation/test (in which case the extra dependencies
              show up only in Build-Depends, not Depends).</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Ok...<br>
    <br>
    Thanks !<br>
    <br>
      Arnaud<br>
  </body>
</html>