Bug#592414: [new check] Warn about Python extension modules linked to libpythonX.Y
On 2011-09-19 14:10, Jakub Wilk wrote:
> tags 592414 + patch
> thanks
>
> * Jakub Wilk <jwilk@debian.org>, 2010-08-09, 23:02:
>> Public Python extension modules, i.e. *.so files in one of these
>> directories:
>>
>> /usr/lib/pyshared/pythonX.Y/
>> /usr/lib/python-support/PACKAGENAME/pythonX.Y/
>> /usr/lib/pythonX.Y/site-packages/
>> /usr/lib/pythonX.Y/dist-packages/
>>
>> should not be linked to libpythonX.Y. Such linkage is not necessary
>> for a module to work correctly and it causes dpkg-shlibdeps to
>> generate dependencies that are too strict. See e.g. bugs #472314,
>> #445411, #445423, #470290.
>>
>> There should be also a separate check (with severity:serious) for the
>> case where a module in a pythonX.Y directory is linked with
>> libpythonZ.W for X.Y != Z.W. See e.g. bug #586937.
>
> Patch attached.
>
Hey,
The part with extensions linked against the wrong version should be
okay. Though as I understood Russ, he (weakly) questioned the part that
relates to the "python-extension-linked-with-libpython" tag.
Does anyone have any concerns with the tag Russ questioned? Russ, do
you feel we should wait with adding the this tag (i.e. only apply the
"first half" of Jakub's patch)?
~Niels
Reply to: