-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.18.0.0 seems to cause misaligned sections #87
Comments
Looking at the logs…it's a bunch of CI chores and a submodule bump. Upstream issue: NixOS/patchelf#492 |
Looks like they're reverting. |
The 0.18.0.0 version has been yanked pending further investigation upstream. |
Any updates on this? 0.18.0 is the current version defined in the |
…ession Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
…ession Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
…ession Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
…ession Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
…ession Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
…ession Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
Co-authored-by: Ryan McCormick <rmccormick@nvidia.com> Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
…ession (#145) Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
Downgrade patchelf version from 0.18.0 to 0.17.2 due to patchelf regression Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
Downgrade patchelf version from 0.18.0 to 0.17.2 due to patchelf regression Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
…ession (#109) Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
This repo just packages the upstream https://github.com/NixOS/patchelf for PyPI to allow pip/pipx/uv install. The 0.18.0 version is already yanked in PyPI. |
Downgrade patchelf version from 0.18.0 to 0.17.2 due to patchelf regression Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
Downgrade patchelf version from 0.18.0 to 0.17.2 due to patchelf regression Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
…ession (#145) Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
…ession (#109) Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
Co-authored-by: Ryan McCormick <rmccormick@nvidia.com> Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87
…ession (#109) (#110) Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87 Co-authored-by: Kyle McGill <101670481+nv-kmcgill53@users.noreply.github.com>
* Update the symlink (#144) * Downgrade patchelf version from 0.18.0 to 0.17.2 due to patchelf regression (#145) Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87 --------- Co-authored-by: Pavithra Vijayakrishnan <160681768+pvijayakrish@users.noreply.github.com> Co-authored-by: Kyle McGill <101670481+nv-kmcgill53@users.noreply.github.com>
Downgrade patchelf version from 0.18.0 to 0.17.2 due to patchelf regression Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87 Co-authored-by: Kyle McGill <101670481+nv-kmcgill53@users.noreply.github.com>
* Update CUDA archs in ORT (#291) * Update CUDA archs in ORT * Update CUDA archs in ORT and fixing typo * Update cudnn home * Version upgrade for openvino updated from 24.12 * Update CUDNN_home for v9.7.0 * Update the home path * Update path * Update CUDNN home * Remove comments * Update the supported igpu NVCC * Update the supported igpu and dgpu NVCC * Upadate default branch post 24.12 (#290) * Update README and versions for 2.53.0 / 24.12 (#288) * Update 'gen_ort_dockerfile.py' fil to meet changes in ONNX Runtime 1.20.x * remove psutils * Update reformating * restore description * Update OpenVINO to 2024.5 (#287) * Update 'gen_ort_dockerfile.py' fil to meet changes in ONNX Runtime 1.20.x * remove psutils * Add OpenVINO version * Fix pre-commit issues * Extract archive in different location (#289) * Extract archive in different location * Revert "Extract archive in different location" This reverts commit e57256a. * Update installation instructions * Reapply "Extract archive in different location" This reverts commit 59e24e4. * Rolling back changes cherry picked from 24.12 * Rolling back changes cherry picked from 24.12: fixing spaces --------- Co-authored-by: Misha Chornyi <99709299+mc-nv@users.noreply.github.com> * Downgrade patchelf version from 0.18.0 to 0.17.2 (#295) Downgrade patchelf version from 0.18.0 to 0.17.2 due to patchelf regression Patchelf shipped a regression in 0.18.0 and has since yanked the pypi release pointing to 0.17.2 as the most recent version. However, 0.18.0 is still the version shipped in both the apt and yum repositories, thus we must use pip to install the version we want. See mayeut/patchelf-pypi#87 --------- Co-authored-by: Pavithra Vijayakrishnan <160681768+pvijayakrish@users.noreply.github.com> Co-authored-by: Kyle McGill <101670481+nv-kmcgill53@users.noreply.github.com>
Our CI started failing today using the
manylinux2014
image. Given the symptom and thedist-info
diff of a single installation (A/D seems to be backwards from what I'd expect):between these two containers:
our generated wheels now have the following error when trying to import our modules:
Something seems to have broken this between 0.17.2.1 and 0.18.0.0.
The text was updated successfully, but these errors were encountered: