On Wed, Nov 1, 2017 at 4:30 PM, John Paul Adrian Glaubitz <glaub...@physik.fu-berlin.de> wrote: > On 11/01/2017 09:19 PM, Gunter Königsmann wrote: >> When dealing with 3rd-party products any change in upstream sane or >> debian might cause breaks, though. > > And? As I said, this happens all the time. Seriously. > > You are phrasing this as if renaming library packages due to > an SO bump is an exception. It isn't.
I don't want to drag this out, since in my opinion this issue is resolved with comment 57. But I think it's worth noting: 1) There was no soname bump here. My understanding of Debian Policy and the Lintian warning is that it does not require renaming existing libraries just to match typical "best practice" naming. Y'all could have waited to rename the library until there was an actual upstream soname bump. (I think the versioned provides takes care of the problem this caused though so never mind now.) 2) Please stop with the criticism of Ubuntu 17.10's early adoption of your sane-backends packaging. Several fixes for the 1.0.27 packaging were only identified by Ubuntu users and fixed by Ubuntu developers. In fact, I think the packaging is in good enough shape that you should consider requesting to start the unstable transition soon. I had a Debian Developer ask when sane-backends 1.0.27 was going to be in unstable since he needs the additional drivers it offers. Thanks, Jeremy Bicha
