On Wed, Nov 1, 2017 at 7:49 PM, John Paul Adrian Glaubitz <glaub...@physik.fu-berlin.de> wrote: > On 11/02/2017 12:18 AM, Jeremy Bicha wrote: > Again, changing library package names due to SO bumps happen all > the time. I don't see why the libsane package should be any different > from other library packages. Yes, there was no SO bump. But the > library package name was not conforming to the Debian Policy either.
There are hundreds of libraries that don't follow "best practice" naming in Debian and in this particular case, the decision to change the library name clearly caused extra headache until we figured out a workaround. My advice in the future is to do like the rest of the Debian Project does and ignore this particular Lintian warning until you actually need to change the library name, unless you are confident that there aren't third parties who are using your library. https://lintian.debian.org/tags/package-name-doesnt-match-sonames.html > and now we > in Debian have to start justifying how we are doing our job in Debian. Hey, if you don't like having to repeatedly justify your rational Debian decisions, maybe I'm getting tired of justifying my rational Ubuntu decisions. My intent with today's email was just to point out that Ubuntu's decision made the Debian package better because we fixed multiple bugs in your packaging that in my opinion would probably otherwise not have been fixed until after you uploaded to unstable Thanks, Jeremy Bicha
