On Feb 9, 2018, at 11:43 AM, Pete Heist <pete@eventide.io> wrote:On Feb 9, 2018, at 8:15 AM, Michael Stapelberg <stapelberg@debian.org> wrote:On Fri, Feb 9, 2018 at 2:09 AM, Pete Heist <pete@eventide.io>wrote: From the original warnings you sent I know I’ve fixed all except "I: irtt source: testsuite-autopkgtest-missing”, but a) I’m not seeing that warning and b) I’m seeing two others. So my questions are: 1) What are your expectations for 'testsuite-autopkgtest-missing', and why am I not seeing it? There are no unit tests to run. Did you apply the ~/.lintianrc I provided? Not doing so would explain the difference. autopkgtest is helpful even if it only compiles the package in question. Why are there no unit tests for your code? :)2) Do you care about 'debian-watch-does-not-check-gpg-signature' and 'no-upstream-changelog’? I do not sign the upstream, and the changes are in README.md, in case those should be split out... They’re not important for the time being. Of course, if you could start signing upstream and provide a separate changelog file, that would be great.Thanks!Ok, I’ve updated the irtt package:- I added a couple high-value unit tests, which also satisfies lintian.- CHANGES.md is split out from README.md to satisfy 'no-upstream-changelog'.
- I tried getting signatures working but punted because GitHub creates a .tar.gz, which I signed with a .tar.gz.asc, but the build process expects a .tar.xz.asc in the upstream, so lintian then warns with 'orig-tarball-missing-upstream-signature'. Is there any pkg-go example of signatures working with a GitHub hosted repo? Otherwise I’ll eventually figure it out.
- I blew away the irtt.git repo and started over so I could just stay on the rails of your dh-make-golang.html blog entry, hope that’s fine.
Let me know if anything else. Thanks!
Pete