On Tue, Nov 10, 2020 at 04:30:07PM +0000, Simon McVittie <s...@debian.org>
wrote:
> On Tue, 10 Nov 2020 at 15:52:26 +0100, Marc Lehmann wrote:
> > If this breakage is indeed intended, maybe debian could simply ship the
> > missing header files (pango/*-private.h)?
>
> Sorry, I don't think it's appropriate for Debian to be unilaterally
> changing Pango's API. If upstream makes these APIs public again, we can
Actually, looking at 1.47 in experimental, it seems the ABI has been
changed without bumping the soname (the size of the PangoFcFontClass
struct has changed, which is part of the publicv ABI), which means
existing binaries will suffer memory corruption.
So debian would at least have to bump the soname to soemthing like 1.1.
This has happened before - pango upstream does not seem to care much about
ABI compatibility, but it's trivial to avoid in debian by bumping the
soname, so old binaries don't cause bad things to happen to users.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
