Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

2017-03-13 Thread Simon McVittie
On Mon, 13 Mar 2017 at 23:43:52 +1100, Scott Leggett wrote: > FYI the version bump originated from this post to the upstream mailing > list[0], which shows upstream's somewhat relaxed attitude to ABI > stability. I guess this is understandable as the libraries are intended > to be private. This

Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

2017-03-13 Thread Scott Leggett
Hi all, Thanks for the bug report and for the thoughful advice. On 2017-03-10.11:18, Vincent Bernat wrote: > ❦ 10 mars 2017 09:29 GMT, Simon McVittie  : > > >> I suppose that's why I am in copy (the other actions are pretty obvious > >> and I suppose Scott will apply them

Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

2017-03-10 Thread Vincent Bernat
❦ 10 mars 2017 09:29 GMT, Simon McVittie  : >> I suppose that's why I am in copy (the other actions are pretty obvious >> and I suppose Scott will apply them soon; I can also do that if he's >> unavailable). > > The other reason I wanted to Cc you is because as sponsor, you were

Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

2017-03-10 Thread Simon McVittie
On Fri, 10 Mar 2017 at 07:53:11 +0100, Vincent Bernat wrote: > I suppose that's why I am in copy (the other actions are pretty obvious > and I suppose Scott will apply them soon; I can also do that if he's > unavailable). The other reason I wanted to Cc you is because as sponsor, you were

Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

2017-03-09 Thread Vincent Bernat
❦ 10 mars 2017 00:18 GMT, Simon McVittie  : > Third bug: libraries with different SONAME versioning packaged together > --- > > Lintian has done its best to advise the maintainer not to do this, but >

Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

2017-03-09 Thread Simon McVittie
(Bringing the sponsor of the last few uploads into Cc) I think there are up to three RC bugs here: * on x86_64, libzebra.so is a broken symlink * on other architectures, every .so is a broken symlink * libraries with different versioning are sharing a package (Policy §8.1) The correct solution

Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

2017-03-08 Thread Andreas Henriksson
Hello, On Mon, Mar 06, 2017 at 01:51:58PM +0100, Andreas Beckmann wrote: > Source: quagga > Version: 1.1.1-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed libquagga-dev contains a > a broken symlink:

Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

2017-03-06 Thread Andreas Beckmann
Source: quagga Version: 1.1.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed libquagga-dev contains a a broken symlink: /usr/lib/x86_64-linux-gnu/libzebra.so -> libzebra.so.0 because libquagga0 ships the following files: