[Debian-med-packaging] Bug#890400: Any news about a new upstream version with new SONAME?

[Andreas Tille]

Hi Julien,

On Wed, Mar 21, 2018 at 09:26:01PM +0100, Julien Yann Dutheil wrote:
> I could somehow udate the symbols list, but still get a lintian warning
> [1].

That was just a typo (see commit 06beb6872bb0c773aff727c25dfe0777a7c401ca).

> I have pushed my commits, would you mind giving them a look? Will
> proceed with other libs once I have confirmation that everything is ok.

I've just uploaded.  I think the following lintian *infos* (lintian -I)
will be interesting for you:

I: libbpp-core source: testsuite-autopkgtest-missing
N: 
N:    This package does not declare a test suite. Having a test suite helps
N:    with automated QA in response to changes in the archive. For example, if
N:    your package has a test suite, it is possible to re-execute that test
N:    suite when any of the package dependencies has a new version and check
N:    whether that update caused problems for your package.
N:    
N:    To declare a test suite, please add a debian/tests/control file to your
N:    package.
N:    
N:    For more information on how to add functional tests to your package,
N:    browse to https://ci.debian.net/doc/.
N:    
N:    Severity: wishlist, Certainty: certain
N:    
N:    Check: testsuite, Type: source

May be you see a chance to tweak the build time test into an autopkgtest.


I: libbpp-core4: spelling-error-in-binary usr/lib/x86_64-linux-gnu/libbpp-core.so.4.0.0 colums columns
I: libbpp-core4: spelling-error-in-binary usr/lib/x86_64-linux-gnu/libbpp-core.so.4.0.0 controled controlled
I: libbpp-core4: spelling-error-in-binary usr/lib/x86_64-linux-gnu/libbpp-core.so.4.0.0 wih with

Please verify your code and simply fix with next upstream release if
these are no false positives.


Kind regards and thanks for your cooperation

       Andreas.

-- 
http://fam-tille.de