Not at all, thank you kindly for patience with my complete newness to this!
Ah, ok. IRTT has an API, but it's not published yet. I think a binary-only package may be better at this point, and a separate source package later when that’s ready? If you agree, could you suggest a simple, current binary package hosted on github as a good example? Debian Code Search? Though its compat version is 8. I just liked how the debian directory is hosted right in the github repo, which brings me to another question... Is it possible to maintain everything on github, or does it need to be on alioth, and if so, what is a good workflow for when I want to pull in changes from upstream for a new release?
Hrm, any idea why I'm seeing large differences in lintian output? I didn’t see any warnings before I posted, but I do see new ones after the .lintianrc changes, just they look completely different... $ cat /etc/debian_version 9.3 $ lintian --version Lintian v2.5.50.4 $ cat .lintianrc display-info = yes display-experimental = yes pedantic = yes show-overrides = no color = auto $ lintian ~/src/github.com/peteheist/irtt/dpkg/irtt_0.9-1_amd64.changes P: irtt source: debian-watch-may-check-gpg-signature I: irtt: hardening-no-fortify-functions usr/bin/irtt I: irtt: spelling-error-in-binary usr/bin/irtt writeN written I: irtt: spelling-error-in-binary usr/bin/irtt ot to I: irtt: hardening-no-bindnow usr/bin/irtt I: irtt: hardening-no-pie usr/bin/irtt P: irtt: no-upstream-changelog Also, some of the warnings (like compat-version) just come from output from dh-make-golang, which I just installed with ‘apt-get install dh-make-golang’. Do I need a newer version?
Ok, that makes sense to me also- received that tip from a different Debian package admin. Thanks! :) |