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

[George Danchev]

On Monday 02 March 2009 00:18:03 Simon Huggins wrote:
> 'ello George,
>
> On Sun, Mar 01, 2009 at 07:32:24PM +0200, George Danchev wrote:
> > I've just commited common symbols file for libburn4 package.
>
> So now I'm confused because it's claiming that every symbol is new in
> 0.6.2.
>
> That can't be true can it?

Good bug report. I incorrectly assumed that the new verison of the library 
also produces common symbols file as claimed by mole for the previous version 
at: http://qa.debian.org/cgi-bin/mole/seedsymbols?pkgname=libburn4

So, we should switch to arch specific symbols files: 
debian/package.symbols.arch

my libburn4.symbols became libburn4.symbols.i386 since I generated it out of 
x86 object files. I suspect that you are building it on amd64, hence 
arch-specific symbols differ. So I also added:

libburn4.symbols.mips
libburn4.symbols.sparc
libburn4.symbols.amd64
libburn4.symbols.powerpc
libburn4.symbols.alpha
libburn4.symbols.hppa
libburn4.symbols.mipsel
libburn4.symbols.s390
libburn4.symbols.armel
libburn4.symbols.ia64
libburn4.symbols.i386    (populated)

Now if you build on amd64 you will still see dpkg-gensymbols show diff with 
new symbols because symbols.amd64 is empty now. You can either patch it or I 
can grab the arch-specific symbols diffs from autobuilders logs.

Let me know if that answers your concerns.

-- 
pub 4096R/0E4BD0AB 2003-03-18 <people.fccf.net/danchev/key pgp.mit.edu>