Comment # 3 on bug 1029902 from Jan Matejek

(In reply to Jan Matejek from comment #2)
> As a workaround, you can build python3 on the same configuration and the
> resulting package will work fine.

...except that it is glibc that is actually doing the call, so s/python3/glibc/

better wait for the update, i suppose