[Rpm-maint] [Rpm-announce] RPM 4.15.0 rc1 released!

[Panu Matilainen]

On 8/31/19 3:09 PM, Thierry Vignaud wrote:
> Le sam. 31 août 2019 à 13:00, Thierry Vignaud <thierry.vignaud at gmail.com 
> <mailto:thierry.vignaud at gmail.com>> a écrit :
> 
>     A wee bit late from the original schedule but at least in the same
>     month
> 
>         still, here comes the first and hopefully last release candidate
>         for 4.15.0.
> 
>         The main highlights since beta are:
>         - Fixed out of order build output
>         - Fixed memory exhaustion during build on 32bit platforms
>         - Added %{expr:...} macro for evaluating expressions (into strings)
>         - Assorted other bug fixes
> 
>         As usual, details and download info at:
> 
>         https://rpm.org/wiki/Releases/4.15.0
> 
>         Unless some major drama comes up, I expect this to become the final
>         release in a couple of weeks.
>         <http://lists.rpm.org/mailman/listinfo/rpm-announce>
> 
> 
>     There's an issue with the python bindings: with the new
>     "rpmdsIsReverse":
> 
>     $ python3
>     (...)
>      >>> import rpm
>     Traceback (most recent call last):
>        File "<stdin>", line 1, in <module>
>        File "/usr/lib64/python3.7/site-packages/rpm/__init__.py", line
>     38, in <module>
>          from rpm._rpm import *
>     ImportError:
>     /usr/lib64/python3.7/site-packages/rpm/_rpm.cpython-37m-x86_64-linux-gnu.so
>     <http://rpm.cpython-37m-x86_64-linux-gnu.so>: undefined symbol:
>     rpmdsIsReverse
> 
> 
> Interestingly, I noted that python[23]-rpm-4.15.0-0.rc1 were linked 
> against librpm*.so.8 instead of .9.
> Rebuilding rpm-4.15 against itself fixes it (aka upgrading first the 
> system rpm to 4.15 before building rpm again).
> So the real issue is that the python modules link against system librpm* 
> instead of the just built librpm*

See https://github.com/rpm-software-management/rpm/issues/130, it's not 
a new issue. AIUI this problem is limited to building bindings with 
setup.py where this sort of in-source situation is not expected at all.

Makes me wonder if we should just scrap the setup.py way of building in 
git master, now that Python 2 support is gone. Wont help with current 
releases of course.

	- Panu -

	- Panu -

	- Panu -