[Debian-ha-maintainers] [corosync] Symbols missing in libsam4 after v1.99.9 (#66)

[Richard B Winters]

On Fri, 2015-04-24 at 00:16 -0700, Fabio M. Di Nitto wrote:
> On 04/24/2015 09:11 AM, Richard Winters wrote:
> > Hello, I was generatiing symbols files for the latest debian
> packages
> > and I discovered that in v1.99.9 symbols were added that went
> missing in
> > v2.3.0:
> 
> I am afraid your script is not working properly. libcmap is there and
> still exports calls such as cmap_initialize.
> 
> 1.99.9 was a pre-release and it's possible that the build system has
> been fixed in the meantime to fix the symbol export list, but they are
> there.
> 
> Fabio

Thanks for the quick reply -


Interesting, I do notice that the symbols reference `cmap_*`, though I
exported them from libsam4-1.99.9-1 along with some new `sam_*` symbols.

```shell
rik at devrikx:~/Documents/mmod/projects/debian/corosync/ubinaries$
dpkg-gensymbols -v1.3.0 -plibsam4
-elibcorosync4_1.3.0-3_amd64/usr/lib/libsam.so.4
-Olibsam4-1.symbolsrik at devrikx:~/Documents/mmod/projects/debian/corosync/ubinaries$ dpkg-gensymbols -v1.4.1 -plibsam4 -elibcorosync4_1.4.1-1_amd64/usr/lib/libsam.so.4 -Olibsam4-1.symbolsrik at devrikx:~/Documents/mmod/projects/debian/corosync/ubinaries$ dpkg-gensymbols -v1.4.2 -plibsam4 -Plibsam4_1.4.2-3_amd64/ -Olibsam4-1.symbolsrik at devrikx:~/Documents/mmod/projects/debian/corosync/ubinaries$ dpkg-gensymbols -v1.4.4 -plibsam4 -Plibsam4_1.4.4-3_amd64/ -Olibsam4-1.symbolsrik at devrikx:~/Documents/mmod/projects/debian/corosync/ubinaries$ dpkg-gensymbols -v1.4.6 -plibsam4 -Plibsam4_1.4.6-1.1_amd64/ -Olibsam4-1.symbolsrik at devrikx:~/Documents/mmod/projects/debian/corosync/ubinaries$ dpkg-gensymbols -v1.99.9 -plibsam4 -Plibsam4_1.99.9-1_amd64/ -Olibsam4-1.symbolsdpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below
dpkg-gensymbols: warning: libsam4-1.symbols doesn't match completely
libsam4-1.symbols
--- libsam4-1.symbols (libsam4_1.99.9_amd64)
+++ dpkg-gensymbolsW_gdUB	2015-04-24 03:21:43.891821453 -0400
@@ -1,9 +1,51 @@
 libsam.so.4 libsam4 #MINVER#
  COROSYNC_SAM_1.0 at COROSYNC_SAM_1.0 1.2.0
+ cmap_context_get at Base 1.99.9
+ cmap_context_set at Base 1.99.9
+ cmap_dec at Base 1.99.9
+ cmap_delete at Base 1.99.9
+ cmap_dispatch at Base 1.99.9
+ cmap_fd_get at Base 1.99.9
+ cmap_finalize at Base 1.99.9
+ cmap_get at Base 1.99.9
+ cmap_get_double at Base 1.99.9
+ cmap_get_float at Base 1.99.9
+ cmap_get_int16 at Base 1.99.9
+ cmap_get_int32 at Base 1.99.9
+ cmap_get_int64 at Base 1.99.9
+ cmap_get_int8 at Base 1.99.9
+ cmap_get_string at Base 1.99.9
+ cmap_get_uint16 at Base 1.99.9
+ cmap_get_uint32 at Base 1.99.9
+ cmap_get_uint64 at Base 1.99.9
+ cmap_get_uint8 at Base 1.99.9
+ cmap_inc at Base 1.99.9
+ cmap_initialize at Base 1.99.9
+ cmap_iter_finalize at Base 1.99.9
+ cmap_iter_init at Base 1.99.9
+ cmap_iter_next at Base 1.99.9
+ cmap_set at Base 1.99.9
+ cmap_set_double at Base 1.99.9
+ cmap_set_float at Base 1.99.9
+ cmap_set_int16 at Base 1.99.9
+ cmap_set_int32 at Base 1.99.9
+ cmap_set_int64 at Base 1.99.9
+ cmap_set_int8 at Base 1.99.9
+ cmap_set_string at Base 1.99.9
+ cmap_set_uint16 at Base 1.99.9
+ cmap_set_uint32 at Base 1.99.9
+ cmap_set_uint64 at Base 1.99.9
+ cmap_set_uint8 at Base 1.99.9
+ cmap_track_add at Base 1.99.9
+ cmap_track_delete at Base 1.99.9
+ sam_data_getsize at Base 1.99.9
+ sam_data_restore at Base 1.99.9
+ sam_data_store at Base 1.99.9
  sam_finalize at COROSYNC_SAM_1.0 1.2.0
  sam_hc_callback_register at COROSYNC_SAM_1.0 1.2.0
  sam_hc_send at COROSYNC_SAM_1.0 1.2.0
  sam_initialize at Base 1.2.0
+ sam_mark_failed at Base 1.99.9
  sam_register at COROSYNC_SAM_1.0 1.2.0
  sam_start at COROSYNC_SAM_1.0 1.2.0
  sam_stop at COROSYNC_SAM_1.0 1.2.0
```

 If those cmap symbol references didn't belong in libsam4 then I think
we're all good, it was just those same cmap symbols that were added in
v1.99.9 that were 'missing' in libsam4-2.3.0.

If it was a pre-release version we can just assume there was an error in
packaging or perhaps in the build? 

Perhaps the script *is* giving me issues, I did do it twice just to be
sure, but that doesn't necessarily mean anything.

Best,


-- 
Rik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/debian-ha-maintainers/attachments/20150424/0ffd85be/attachment.sig>