potiuk commented on code in PR #59658:
URL: https://github.com/apache/airflow/pull/59658#discussion_r2637040952


##########
Dockerfile.ci:
##########
@@ -988,9 +988,9 @@ function install_airflow_when_building_images() {
     set +x
     common::install_packaging_tools
     echo
-    echo "${COLOR_BLUE}Running 'pip check'${COLOR_RESET}"
+    echo "${COLOR_BLUE}Running 'uv pip check'${COLOR_RESET}"
     echo
-    pip check
+    uv pip check

Review Comment:
   Yes. Looks like a bug in `pip check`:
   
   The `pagefind-bin` gets happily installed even by pip but then `pip check` 
complains:
   
   ```
   [Breeze:3.10.19] root@f6bc09f07a77:/opt/airflow$ pip install pagefind-bin
   Collecting pagefind-bin
     Downloading 
pagefind_bin-1.4.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64.whl.metadata
 (1.0 kB)
   Downloading 
pagefind_bin-1.4.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64.whl
 (9.4 MB)
      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 9.4/9.4 MB 48.6 MB/s  0:00:00
   Installing collected packages: pagefind-bin
   Successfully installed pagefind-bin-1.4.0
   WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager, possibly rendering your 
system unusable. It is recommended to use a virtual environment instead: 
https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you 
know what you are doing and want to suppress this warning.
   [Breeze:3.10.19] root@f6bc09f07a77:/opt/airflow$ pip check
   pagefind_bin 1.4.0 is not supported on this platform
   ```
   
   My guess is that the multi-architecture whell (first time I see wheel that 
is supporting both glibc and musl) - is not properly recognised as glibc 
compatible.
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to