On 11/11/14 10:08, Fabian Greffrath wrote:
> On Mon, 10 Nov 2014 21:44:58 +0100 Pino Toscano <p...@debian.org> wrote:
>> Please drop this NMU, since the approach chosen (bumping shlibs for
>> everybody) is not correct.
If the new symbol is public API that (in principle) other packages could
use, which AFAICS it is, then I think the only solution that doesn't
involve bumping shlibs for everyone is a symbols file. It could probably
be as simple as something like this (untested, syntax might be wrong):
libpoppler.so.46 libpoppler46 #MINVER#
* Build-Depends-Package: libpoppler-dev
(c++)"GfxFont::getAlternateName(char const*)" 0.26.5-2~
(regex)"." #CURVER#
to assign a different version for that one symbol?
On 11/11/14 10:08, Fabian Greffrath wrote:
> We solved this by calling dh_makeshlibs twice: First, before calling
> dh_shlibdeps, with very strict dependency information. And then again,
> after calling dh_shlibdeps, with the relaxed dependency information
> that other packages should see.
For symbols that are considered private to the source package, that
seems unnecessarily complex; you can use debian/shlibs.local to give
binary packages within the same source package a strict dependency.
S
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
