Le vendredi 05 août 2005 à 07:16 -0600, Barak Pearlmutter a écrit : > Problem is what does "fix djvulibre" mean here? > > Fix it to generate the old soname, thus losing soname compatibility > with upstream? > > Fix it to generate a different library name, perhaps libdjvulibre15? > > Fix it by asking upstream to stop changing the soname for no reason? > > Fix it by convincing anyone using the library that they need an exact > version dependency, which is what upstream recommends library users > do, and encourages by changing the soname all the time? > > Okay, I will change the generated library to libdjvulibre15.
Hum, I didn't notice you are the maintainer for djvulibre. Have you read the library packaging guide? The package name for libname.so.<soname> has to be libname<soname>, you have here a perfect example of why. Why does djvulibre changed its soname between 2 revision of the package to start? Has the ABI/API changed? Anyway that's a question for upstream. The packaging issue is that your package has to be renamed to follow the soname change. Could you reupload a libdjvulibre14 with the previous soname and then a new revision which update the lib and change the package name? This way libdjvulibre14 is fixed and you get the new version with the right package. Cheers, Sebastien Bacher
