Question about binNMU and transition, how can this package NOT segfault?
Gianfranco Costamagna <costamagnagianfranco <at> yahoo.it>
2014-04-23 08:10:26 GMT
Hi Debian Developers,
A while ago sdlgfx  package changed the API/ABI, and for this reason we started a transition from .23 to
the new package has been uploaded on unstable (after two experimental releases), on
[2014-04-07] Accepted 2.0.25-3 in unstable (medium)
so after that time every package uploaded on debian has been built with the new soname.
Another package (just an example) is this one, gambas3  that uses sdlgfx as B-D
that has been uploaded on unstable on
[2014-04-11] Accepted 3.5.2-2 in unstable (low)
So you might see that everything is correct, but (please correct me if I'm wrong)
I see TWO bugs:
-gambas3 reached testing prior to sdlgfx 2.0.25, so how can people installing it be sure the package won't
segfault for the library change?
-gambas3 has been uploaded on debian after TWO weeks in new queue, so the amd64 package has been built on
Date: Wed, 02 Apr 2014 16:23:48 +1100
the situation now is:
gambas3 for amd64 still uses the old sdlgfx
for other archs uses the new API/ABI,
it has reached testing for an unknown reason to me