Bug 2000022 - /usr/bin/python3: symbol lookup error: /lib64/libpython3.10.so.1.0: undefined symbol: close_range, version GLIBC_2.34
Summary: /usr/bin/python3: symbol lookup error: /lib64/libpython3.10.so.1.0: undefined...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: python3.10
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Python Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-01 08:25 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2021-09-01 10:15 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-09-01 08:34:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Zbigniew Jędrzejewski-Szmek 2021-09-01 08:25:50 UTC
Description of problem:
In rawhide mock (on F33, not sure if that matters), I get $subject as error when I execute python3.

Version-Release number of selected component (if applicable):
python3-3.10.0~rc1-1.fc35.x86_64
glibc-2.33.9000-36.fc35.x86_64

How reproducible:
Deterministic

Steps to Reproduce:
1. mock --shell
2. python3

Comment 1 Zbigniew Jędrzejewski-Szmek 2021-09-01 08:34:41 UTC
I renitiailized the mock chroots, and I get a newer glibc:

<mock-chroot-f35> sh-5.1# rpm -q python3 glibc
python3-3.10.0~rc1-1.fc35.x86_64
glibc-2.34-1.fc35.x86_64

<mock-chroot-rawhide> sh-5.1# rpm -q python3 glibc
python3-3.10.0~rc1-1.fc35.x86_64
glibc-2.34.9000-4.fc36.x86_64

and in both cases python3 works. So it seems that the original issue was caused
by some stale mock definition. I'll close this, even though it seems that some version
dependency is missing somewhere.

Comment 2 Miro Hrončok 2021-09-01 10:15:17 UTC
> even though it seems that some version dependency is missing somewhere.

Yes, newer glibc now has a requirements generator to avoid this in the future. Se https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/MENH65L5JJLMT7JGN4LB2L67WXRFW6ZT


Note You need to log in before you can comment on or make changes to this bug.