OK, it works for me too.
> I've also explicitly removed the .symbols file as I found the Policy ManualPlease add a lintian override for this:
> explicitly talks about C++ libraries in the last paragraph of section 8.6 (
> http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-depends
> ):
libcapnp-0.2.0: no-symbols-control-file usr/lib/libcapnp-0.2.0.so
> Last of all, I've just built & uploaded a new build of 0.2.0-1 with theSo, a few other comments:
> changes you suggested in your original review, plus the changes discussed
> in this email:
>
> http://mentors.debian.net/debian/pool/main/c/capnproto/capnproto_0.2.0-1.dsc
>
> Thanks! Please let me know if I can do anything else to move this forward.
- Remove the comments at the top of debian/rules, they clutter it and
they do not match the content (since you are using the tiny debhelper
set). Don't even keep the DH_VERBOSE stuff
- The hardening stuff does not seem to work correctly. Maybe you could
just try with debhelper 9 and debian/compat to 9 to have them apply
automatically.
- Use DEP3 (http://dep.debian.net/deps/dep3/) to describe the patchs
that you add (with Author, Description and Forwarded fields).
- You ship the .la file and empty the dependency_libs field. I think
that you can just not ship it at all. There was a release goal to
remove them. Since you don't have any reverse dependency, it is
better to not ship it.
- You use --with python2. I don't see any Python files in the resulting
packages. Therefore, you don't need to use dh_python2. I suppose
Python is only used in tests. Just keep it as a Build-Depends.
- In debian/control, don't start the short description with a capital
for capnproto.