Re: package with new soname: questions about .symbols and uploading

2011-07-15 Thread Johan Van de Wauw
On Thu, Jul 14, 2011 at 8:48 PM, Jakub Wilk wrote: > * Kilian Krause , 2011-07-14, 20:34: >> >> If you can confirm that the symbols file for your last version and this >> version match up perfectly, then the SONAME shouldn't have been bumped in >> the first place > > Err, no, you can't conclude th

Re: package with new soname: questions about .symbols and uploading

2011-07-14 Thread Kilian Krause
Hi Jakub, On Thu, 2011-07-14 at 20:48 +0200, Jakub Wilk wrote: > * Kilian Krause , 2011-07-14, 20:34: > >If you can confirm that the symbols file for your last version and this > >version match up perfectly, then the SONAME shouldn't have been bumped > >in the first place > > Err, no, you can't

Re: package with new soname: questions about .symbols and uploading

2011-07-14 Thread Jakub Wilk
* Kilian Krause , 2011-07-14, 20:34: If you can confirm that the symbols file for your last version and this version match up perfectly, then the SONAME shouldn't have been bumped in the first place Err, no, you can't conclude that ABI wasn't broken just from the fact that symbol lists didn't

Re: package with new soname: questions about .symbols and uploading

2011-07-14 Thread Kilian Krause
Johan, On Thu, Jul 14, 2011 at 11:31:04AM +0200, Johan Van de Wauw wrote: > I've packaged a new version of my library package 'libharu'. Since > upstream uses a -RELEASE type of version number, I copied this, and > this resulted in a libhpdf-2.1.0 package. > I've now updated my package to version

Re: package with new soname: questions about .symbols and uploading

2011-07-14 Thread Paul Wise
On Thu, Jul 14, 2011 at 11:31 AM, Johan Van de Wauw wrote: > But I still want to fix the .symbols file. However, I was not able to > find how I should do it in this case (new packagename). Symbols files are mainly useful when one SONAME/package name lasts longer than one Debian release cycles.

Re: package with new soname: questions about .symbols and uploading

2011-07-14 Thread Gergely Nagy
> But I still want to fix the .symbols file. However, I was not able to > find how I should do it in this case (new packagename). > Should I just generate a new file from scratch (I have not seen > incompatible api changes) or refer to the old version number for > functions which were available bef

package with new soname: questions about .symbols and uploading

2011-07-14 Thread Johan Van de Wauw
Dear mentors, I've packaged a new version of my library package 'libharu'. Since upstream uses a -RELEASE type of version number, I copied this, and this resulted in a libhpdf-2.1.0 package. I've now updated my package to version 2.2.1. It builds these binary packages: libhpdf-2.2.1 - C library f