[Debian-med-packaging] Bug#897780: Bug#897785: Bug#897784: Bug#897780: Now gcc-8 errors caused by non-fitting symbols file became serious

[Andreas Tille]

[CC only bug of libbpp-core to reduce the noise on the mailing list a bit]

Dear Julien,

On Wed, Aug 22, 2018 at 09:14:49AM +0200, Julien Yann Dutheil wrote:
> 
> Library updates should be now done and pushed.

I've just checked libbpp-core and realised that pristine-tar information
is missing.  Did you simply forgot to push or it is not imported.  I
recently gave some hints about this[1] here on this list.  Feel free to
ask if you have no idea what to do anyway.

> Some notes:
> - I referred to the bug numbers in commits and changelogs, but did not
> close them, as the report says to only close them once the packages build
> properly.

Please use Close statements.  I'm building those packages here at my
side in a chroot and if they will not upload - but if it builds the bug
can be closed.  I like your good style to add some extra care but in
this case it is not needed.

> - I am regularly facing random issues like package "bpp-*-dev not found" or
> "library symbols contain debian version number". I came to realise that
> changing d-shlibs (>= 0.80) or (>=0.82) solves the problem: if it fails
> with one, I change the number and it works. When it fails again, I change
> the number back and it works again.

That's strange.  When building in an up to date unstable chroot you
should get d-shlibs 0.82+nmu1 whatever Build-Depends you are using.  The
Build-Depends is only useful for backports to other systems where some
lower version of d-shlibs might be used and the build would fail.  So
you are probably building on a different system than Debian unstable and
moreover you have some interesting effect in your preferences which are
able to pick different versions of d-shlibs (I've never seen this but
who knows).

> I have no idea what's going on and I
> must obviously be doing sthg wrong... would you mind checking I did not
> mess anything in the control files?

I do not think that the problem is inside the control file but in your
build system.  If you want more detailed help I need the exact package
and the positive + negative versioned Build-Depends.

Summary of the blockers for an upload:

   1. pristine-tar
   2. s/Ref:/Closes:/ in d/changelog

Once you are touching the packages again please also set latest
Standards-Version:

   3. Standards-Version: 4.2.0

Kind regards and thanks for the preparation of the packages

       Andreas.


[1] https://alioth-lists.debian.net/pipermail/debian-med-packaging/2018-August/064878.html

-- 
http://fam-tille.de