Re: Newbie questions on packaging opencpn

[Sebastiaan Couwenberg <sebastic@xs4all.nl>]

On 9/2/18 6:53 PM, Sebastiaan Couwenberg wrote:
> Make sure that you configure the lintian hook and always build your
> packages in a cowbuilder chroot, as documented in the policy, this
> points out many issues with packages. See:
> 
>  https://debian-gis-team.pages.debian.net/policy/packaging.html#git-pbuilder

Have you configured your build environment with the lintian hook as
documented in the team policy?

There are some lintian issues that need to be addressed:

 I: unarr source: testsuite-autopkgtest-missing

There is value to autopkgtests, but can be quite time consuming to
setup. If you're not going to add autopkgtests in the near future, add
an override with comment to suppress this issue.

 X: unarr source: upstream-metadata-file-is-missing

You should consider adding an upstream metadata file, to at least
documented the upstream repository & bug URLs.

 I: unarr source: debian-watch-file-is-missing

This needs an override until a watch file can be added after upstream
starts tagging releases.

 I: libunarr1: hardening-no-bindnow
usr/lib/x86_64-linux-gnu/libunarr.so.1.0.0

Enable all hardening buildflags in debian/rules with:

 # Enable hardening build flags
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all

 I: libunarr1: no-symbols-control-file
usr/lib/x86_64-linux-gnu/libunarr.so.1.0.0

Since it's a C library adding a symbols files is a must, for C++
libraries `dh_makeshlibs -V` or pkgkde-symbolshelper should be used.

Kind Regards,

Bas