Control: found -1 1.0.1-3 On Wed, 20 Aug 2014 13:19:46 +0000 Pierre Chifflier <pol...@debian.org> wrote: nistrators by mailing ftpmas...@ftp-master.debian.org) > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Format: 1.8 > Date: Wed, 20 Aug 2014 14:58:53 +0200 > Source: liblognorm > Binary: liblognorm-dev liblognorm1 > Architecture: source amd64 > Version: 1.0.1-3 > Distribution: unstable > Urgency: medium > Maintainer: Pierre Chifflier <pol...@debian.org> > Changed-By: Pierre Chifflier <pol...@debian.org> > Description: > liblognorm-dev - Log normalizing library > liblognorm1 - Log normalizing library > Closes: 753510 > Changes: > liblognorm (1.0.1-3) unstable; urgency=medium > . > * Move lognormalizer exe to arch-specific directory, drop conflict against > liblognorm0, and make package Multi-arch:Same (Closes: #753510)
This does not really address the issue pointed out by Bastian, so I'm reopening this bug report. Installing the binary as /usr/lib/$(DEB_HOST_MULTIARCH)/liblognorm/lognormalizer still means you get the file conflict on each soname bump. I would suggest moving the binary into a separate binary package, say liblognorm-utils, as it is the cleanest solution after all. The next soname bump (which will happen for the upcoming 1.1.4) is a good opportunity to split the binary out into a new binary package as it will have to pass NEW anyway in that case. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
