[ 
https://issues.apache.org/jira/browse/FLINK-38130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18008946#comment-18008946
 ] 

Ferenc Csaky commented on FLINK-38130:
--------------------------------------

Hi! AFAIK this is not a bug, but a feature. I did not write the Nightly 
trigger, it was done in FLINK-34487. But what's happening here is that, for 
Linux previously we did not use {{cibuildwheel}} to produce the wheel files, 
but we had a [custom 
script|https://github.com/apache/flink/blob/master/flink-python/dev/build-wheels.sh]
 that handles the installation. The [GH workflow 
script|https://github.com/apache/flink/blob/bf1cd860617f7b51ac91516814c0e931e5bba241/.github/workflows/nightly.yml#L111]
 uses {{manylinux2014}} as the base image for Linux, and then {{auditwheel 
repair}} will include every manylinux tags that the end result is compatible 
with. cc [~dianfu] to verify

Some additional ChatGPT knowledge:

{quote}
Your wheel has multiple manylinux tags because:
* You're building on manylinux2014 (glibc 2.17).
* It's backward compatible with older standards like manylinux1.
* Your wheel is compatible with older glibc versions (2.5).
* auditwheel tags the wheel with all compatible standards for maximum 
compatibility.

If you want to limit tags (e.g. to only manylinux2014), you'd have to build in 
a way that uses newer symbols or dependencies that require glibc 2.17+, but in 
most cases this multi-tagging is beneficial.
{quote}

> The python linux wheel package name is duplicated
> -------------------------------------------------
>
>                 Key: FLINK-38130
>                 URL: https://issues.apache.org/jira/browse/FLINK-38130
>             Project: Flink
>          Issue Type: Bug
>          Components: API / Python, Release System
>    Affects Versions: 2.1.0, 2.2.0
>            Reporter: dalongliu
>            Priority: Blocker
>             Fix For: 2.1.0, 2.2.0
>
>         Attachments: image-2025-07-22-15-50-29-446.png, 
> image-2025-07-22-15-50-49-758.png
>
>
> The corrupt package name:
>  !image-2025-07-22-15-50-29-446.png! 
> The correct package name:
>  !image-2025-07-22-15-50-49-758.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to