[Pkg-libburnia-devel] adding symbol files to the burn library packages

George Danchev danchev at spnet.net
Mon Mar 2 16:49:45 UTC 2009

Ok here is the plan explained:

1) upload libburn 0.6.2-3 with symbols files added (only libburn4.symbols.i386 
is populated by me for obvious reasons)
2) wait for autobuilders to complete and grab symbols diffs from their build 
logs and patch the empty symbols files. 
3) add the new upstream release of libburn, build the package and see what 
dpkg-gensymbols has to show us.
4) if everyting is as expected, upload that new upstream release.

We can not grab the symbols diffs from the current autobuilders logs since 
symbols files haven't been in the package proper, so dpkg-gensymbols hasn't 
been triggered by dh_makeshlibs, at all.

Does that plan make sense?

A simplified version of that plan would be to perform only 3) and 4) but we 
won't have the rest of symbols.$ARCH populated and ready to be compared with, 
thus we will only see dpkg-gensymbols comparing symbols for i386 build (since 
its symbols file libburn4.symbols.i386 is already in place) and the whole new 
symbols for the rest of architectures whoever/whatever builds them.

More information about the Pkg-libburnia-devel mailing list