Re: The next upload of libpisock9 will Breaks: many packages

2009-07-20 Thread Ludovic Rousseau
Michael Biebl a écrit : Ludovic Rousseau wrote: Hello, The new upstream version of pilot-link 0.12.4 is not ABI backward compatible. And upstream broke the ABI and forgot to change the soname. then why don't you just bump the soname yourself. That's imho the only sane and maintainable opti

Re: The next upload of libpisock9 will Breaks: many packages

2009-07-19 Thread Michael Biebl
Ludovic Rousseau wrote: > Hello, > > The new upstream version of pilot-link 0.12.4 is not ABI backward > compatible. And upstream broke the ABI and forgot to change the soname. > then why don't you just bump the soname yourself. That's imho the only sane and maintainable option. Change the sona

Re: The next upload of libpisock9 will Breaks: many packages

2009-07-19 Thread Bastian Blank
On Sun, Jul 19, 2009 at 09:56:41AM +0200, Bastian Blank wrote: > On Sat, Jul 18, 2009 at 11:48:58PM +0200, Ludovic Rousseau wrote: > > The new upstream version of pilot-link 0.12.4 is not ABI backward > > compatible. And upstream broke the ABI and forgot to change the soname. > Then _you_ have to

Re: The next upload of libpisock9 will Breaks: many packages

2009-07-19 Thread Bastian Blank
On Sat, Jul 18, 2009 at 11:48:58PM +0200, Ludovic Rousseau wrote: > The new upstream version of pilot-link 0.12.4 is not ABI backward > compatible. And upstream broke the ABI and forgot to change the soname. Then _you_ have to change it, instead of doing stupid things with Breaks. Or how do you

The next upload of libpisock9 will Breaks: many packages

2009-07-18 Thread Ludovic Rousseau
Hello, The new upstream version of pilot-link 0.12.4 is not ABI backward compatible. And upstream broke the ABI and forgot to change the soname. I reported a bug to every Debian package depending on libpisock9 asking for recompiling with libpisock9 0.12.4 instead of 0.12.3. pilot-qof (libp