<div dir="ltr">Dear Andreas,<div><br></div><div>I moved forward with libbpp-seq, but after pushing I got the following message:</div><div><br></div><div>remote: Resolving deltas: 100% (172/172), completed with 152 local objects.<br>remote: <br>remote: To create a merge request for pristine-tar, visit:<br>remote: <a href="https://salsa.debian.org/med-team/libbpp-seq/merge_requests/new?merge_request%5Bsource_branch%5D=pristine-tar">https://salsa.debian.org/med-team/libbpp-seq/merge_requests/new?merge_request%5Bsource_branch%5D=pristine-tar</a><br>remote: <br>remote: To create a merge request for upstream, visit:<br>remote: <a href="https://salsa.debian.org/med-team/libbpp-seq/merge_requests/new?merge_request%5Bsource_branch%5D=upstream">https://salsa.debian.org/med-team/libbpp-seq/merge_requests/new?merge_request%5Bsource_branch%5D=upstream</a><br>remote: <br><br></div><div>Clicking on the suggested links leads to a 404 error (I do not have permission to access this page).<br><br></div><div>Is everything ok or did I somehow do sthg wrong?<br><br></div><div>Best,<br><br></div><div>Julien.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 22, 2018 at 11:17 AM, Julien Yann Dutheil <span dir="ltr"><<a href="mailto:julien.dutheil@univ-montp2.fr" target="_blank">julien.dutheil@univ-montp2.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Andreas,<div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Mar 22, 2018 at 10:17 AM, Andreas Tille <span dir="ltr"><<a href="mailto:tille@debian.org" target="_blank">tille@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Julien,<br>
<span><br>
On Wed, Mar 21, 2018 at 09:26:01PM +0100, Julien Yann Dutheil wrote:<br>
> I could somehow udate the symbols list, but still get a lintian warning<br>
> [1].<br>
<br>
</span>That was just a typo (see commit 06beb6872bb0c773aff727c25dfe07<wbr>77a7c401ca).<br>
<span><br></span></blockquote></span><div>Ok, thanks.</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
> I have pushed my commits, would you mind giving them a look? Will<br>
> proceed with other libs once I have confirmation that everything is ok.<br>
<br>
</span>I've just uploaded. I think the following lintian *infos* (lintian -I)<br>
will be interesting for you:<br>
<br>
I: libbpp-core source: testsuite-autopkgtest-missing<br>
N:<br>
N: This package does not declare a test suite. Having a test suite helps<br>
N: with automated QA in response to changes in the archive. For example, if<br>
N: your package has a test suite, it is possible to re-execute that test<br>
N: suite when any of the package dependencies has a new version and check<br>
N: whether that update caused problems for your package.<br>
N:<br>
N: To declare a test suite, please add a debian/tests/control file to your<br>
N: package.<br>
N:<br>
N: For more information on how to add functional tests to your package,<br>
N: browse to <a href="https://ci.debian.net/doc/" rel="noreferrer" target="_blank">https://ci.debian.net/doc/</a>.<br>
N:<br>
N: Severity: wishlist, Certainty: certain<br>
N:<br>
N: Check: testsuite, Type: source<br>
<br>
May be you see a chance to tweak the build time test into an autopkgtest.<br>
<br></blockquote></span><div>Humm... not sure how that integrates with our existing series of unit tests at build time?</div><span class=""><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I: libbpp-core4: spelling-error-in-binary usr/lib/x86_64-linux-gnu/libbp<wbr>p-core.so.4.0.0 colums columns<br>
I: libbpp-core4: spelling-error-in-binary usr/lib/x86_64-linux-gnu/libbp<wbr>p-core.so.4.0.0 controled controlled<br>
I: libbpp-core4: spelling-error-in-binary usr/lib/x86_64-linux-gnu/libbp<wbr>p-core.so.4.0.0 wih with<br>
<br>
Please verify your code and simply fix with next upstream release if<br>
these are no false positives.<br>
<br></blockquote></span><div>Wow, impressive! Fixed upstream. fortunately, no interface break :) </div><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Kind regards and thanks for your cooperation<br>
<span class="m_-2825933216083736670HOEnZb"><font color="#888888"><br></font></span></blockquote></span><div>Thanks a lot for your patience and advice!</div><div><br></div><div>Julien. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="m_-2825933216083736670HOEnZb"><font color="#888888">
Andreas.<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
<a href="http://fam-tille.de" rel="noreferrer" target="_blank">http://fam-tille.de</a><br>
<br>
</font></span></font></span></blockquote></div><span class=""><br><br clear="all"><div><br></div>-- <br><div class="m_-2825933216083736670gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Julien Y. Dutheil, Ph-D<br>0 <a href="tel:+49%206421%20178986" value="+496421178986" target="_blank">(+49) 6421 178 986</a><div><br>§ Max Planck Institute for Evolutionary Biology<div>Molecular Systems Evolution</div><div>Department of Evolutionary Genetics</div><div>Plön -- GERMANY<br></div><br>§ Institute of Evolutionary Sciences - Montpellier<br>University of Montpellier 2 -- FRANCE</div></div></div></div></div>
</span></div></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Julien Y. Dutheil, Ph-D<br><div>0 (+49) 4522 763 298<br><br>§ Max Planck Institute for Evolutionary Biology</div><div>Molecular Systems Evolution</div><div>Department of Evolutionary Genetics</div><div>Plön -- GERMANY<br></div><div><br>§ Institute of Evolutionary Sciences - Montpellier<br>University of Montpellier 2 -- FRANCE</div></div></div></div></div>
</div>