[Pkg-samba-maint] Bug#972912: Bug#972912: Incorrect fix to bug

[Mathieu Parent]

Le jeu. 17 déc. 2020 à 16:48, Sven Mueller <sven.mueller72 at gmail.com> a écrit :
>
> Hi Mathieu.

Hi,

> Just wanted to say that your fix here seems wrong:
> The symbols file says when a specific symbol for a specific lib was added.
> If I rebuild ldb against Python 3.9, it will suddenly claim that - for example -  symbol PYLDB_UTIL_2.1.0 at PYLDB_UTIL_2.1.0 was added to the package - for the Python 3.9 specific lib - in package version 2:2.1.0 - Even though that package version was not built against Python 3.9 at all.
>
> The better fix would be to explicitly build against specific Python versions (python3.8-dev, python3.9-dev build dependencies) and have appropriate symbols listed for both of them.
>
> Currently, if a package builds against the ldb python bindings for Python 3.9, it will generate versioned dependencies that are incorrect (if all it uses would be the above symbol, it would depend on python3-ldb >= 2:2.1.0 - which didn't have any Python 3.9 bindings) - and fail after installation.
>
> To be fair though, I'm not even sure having the symbols file for the python bindings .so files makes much sense.

OK. Could you submit a merge request fixing this? SInce the migration
to python3, the bindings are getting complicated. Any help here is
apprecciated.

Regards

Mathieu Parent