Ack, merge request created.
I had already built ldb with the patch for both unstable and the
environment I ran into issues due to the symbols check and also rebuilt
samba in both afterwards. Both built fine and at least basic functionality
tests also worked fine.
Am Fr., 8. Jan. 2021 um 13:33 Uhr
Le lun. 21 déc. 2020 à 16:06, Sven Mueller a écrit :
>
> Well, turns out that apparently nobody else bothers with a .symbols file for
> Python extensions. I looked at the packages for samba, numpy, mypy and
> python-stdlib-extensions. And if the Python maintainers themselves don't do
> it, you
Well, turns out that apparently nobody else bothers with a .symbols file
for Python extensions. I looked at the packages for samba, numpy, mypy and
python-stdlib-extensions. And if the Python maintainers themselves don't do
it, you probably shouldn't.
I attached a diff to remove the relevant file
Le jeu. 17 déc. 2020 à 16:48, Sven Mueller 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
Hi Mathieu.
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@PYLDB_UTIL_2.1.0 was added to the
package - for the Py
5 matches
Mail list logo
