[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

how to check for binary compability?

Hello again,

This is the third time I'm writing to debian-mentors. I don't know why
nobody replied to my former mails, but maybe I didn't describe the
problem good enough, or the answers to my questions where to obvious.

At packaging mimelib1 from standalone-source I patched the sources to
use strncpy/strncat instead of strlcpy/strlcpy along with several other

Now I tried to check for binary compability with libmimelib1c2a packages
from kdepim 3.5.9 sources. To do that, I compared the output of
'objdump -T /usr/lib/libmimelib.so.1 | grep \\.text | cut -b62-'

Unfortunately there are differences. Now I simply don't know if these
differences render the package binary incompatible, or whether they
don't matter at all.

The patches against mimelib sources don't change any struct or functions
to my knowledge.

Now what to do about it? should I simply bump the soname and binary
package names (from 1 to 2) and request binNMUs for reverse depends?
Or is there a way to keep ABI compability with the help of something
like a symbols file?

I attached the diff for output of objdump -T. diff is between the
libmimelib1c2a package from kdepim 3.5.9 sources (debian/lenny), and my
own standalone source package with no source changes other than
strlcat/strlcpy -> strncat/strncpy.


--- objdump_sid_libmimelib1c2a_1.1.2_kde	2009-04-27 16:44:22.000000000 +0200
+++ objdump_sid_libmimelib1c2a_1.1.2	2009-04-28 15:00:15.000000000 +0200
@@ -68,7 +68,6 @@
@@ -152,7 +151,6 @@
@@ -222,6 +220,7 @@
@@ -230,6 +229,7 @@
@@ -296,6 +296,7 @@
@@ -398,6 +399,7 @@
@@ -550,7 +552,6 @@
@@ -606,6 +607,7 @@
@@ -722,9 +724,11 @@
@@ -872,7 +876,6 @@

Reply to: