Dear Andreas, I moved forward with libbpp-seq, but after pushing I got the following message:
remote: Resolving deltas: 100% (172/172), completed with 152 local objects. remote: remote: To create a merge request for pristine-tar, visit: remote: https://salsa.debian.org/med-team/libbpp-seq/merge_requests/new?merge_request%5Bsource_branch%5D=pristine-tar remote: remote: To create a merge request for upstream, visit: remote: https://salsa.debian.org/med-team/libbpp-seq/merge_requests/new?merge_request%5Bsource_branch%5D=upstream remote: Clicking on the suggested links leads to a 404 error (I do not have permission to access this page). Is everything ok or did I somehow do sthg wrong? Best, Julien. On Thu, Mar 22, 2018 at 11:17 AM, Julien Yann Dutheil < julien.duth...@univ-montp2.fr> wrote: > Hi Andreas, > > On Thu, Mar 22, 2018 at 10:17 AM, Andreas Tille <ti...@debian.org> wrote: > >> 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 06beb6872bb0c773aff727c25dfe07 >> 77a7c401ca). >> >> Ok, thanks. > > >> > 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. >> >> Humm... not sure how that integrates with our existing series of unit > tests at build time? > > 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. >> >> Wow, impressive! Fixed upstream. fortunately, no interface break :) > >> >> Kind regards and thanks for your cooperation >> >> Thanks a lot for your patience and advice! > > Julien. > >> Andreas. >> >> -- >> http://fam-tille.de >> >> > > > -- > Julien Y. Dutheil, Ph-D > 0 (+49) 6421 178 986 <+49%206421%20178986> > > § Max Planck Institute for Evolutionary Biology > Molecular Systems Evolution > Department of Evolutionary Genetics > Plön -- GERMANY > > § Institute of Evolutionary Sciences - Montpellier > University of Montpellier 2 -- FRANCE > -- Julien Y. Dutheil, Ph-D 0 (+49) 4522 763 298 § Max Planck Institute for Evolutionary Biology Molecular Systems Evolution Department of Evolutionary Genetics Plön -- GERMANY § Institute of Evolutionary Sciences - Montpellier University of Montpellier 2 -- FRANCE
