Le mercredi 08 février 2017 à 17:48 +0500, Andrey Rahmatullin a écrit : > On Wed, Feb 08, 2017 at 01:21:13PM +0100, Sébastien Villemot wrote: > > By the way, does this bug really warrant a serious severity? I could not > > find anything in the Policy mandating proper linking of shared libraries > > within the same package. > You are correct, "within the same package" is not a part of the > requirement. > Besides the Policy requirement of "shared libraries must be linked against > all libraries that they use symbols from in the same way that binaries > are" in 10.2 there is an additional "Shared libraries must normally be > linked with all libraries they use symbols from" requirement in > https://release.debian.org/stretch/rc_policy.txt.
Thanks. I had overlooked the requirement spelled out in Policy §10.2. Actually it confirms that this bug is actually of RC severity. I don't know what's the proper solution to this issue. The circularity can easily be dealt with (using patchelf for closing the loop in DT_NEEDED entries). The problem is rather that the Cblacs_pinfo symbol is provided by two alternative (and mutually exclusive) libraries. Input from the maintainer would be helpful here. -- .''`. Sébastien Villemot : :' : Debian Developer `. `' http://sebastien.villemot.name `- GPG Key: 4096R/381A7594
