Package: libtasn1-2 Version: 0.3.1-1 Severity: grave libtasn1-2 changed the so-name and must therefore change the binary package name.
The conflict with libgnutls12 (<< 1.3.5) was a nice try, but it isn't correct and can cause breakge. An example where this will break horribly: $ objdump -p /usr/bin/gsasl Dynamic Section: ... NEEDED libgnutls.so.12 NEEDED libtasn1.so.2 ... You could conflict woth all package versions that do or did depend on libtasn1-2, but even in the best case it is only as good as a renaming of the library package. Yes, due to the known shortcomings of testing such library transitions are a pain for your release team, but this is the only technically way to solve this properly, and the release team has freely chosen to use testing despite it's known shortcomings. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
