-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Pin pip to version 24.2, and update disable-non-manylinux.patch #19510
Pin pip to version 24.2, and update disable-non-manylinux.patch #19510
Conversation
The code logic in this area has changed, resulting in patch conflicts. Signed-off-by: Saikrishna Arcot <[email protected]>
This is needed because the patch file that has been updated can only be applied to 24.1.2. However, the version pinning for 24.0 will mean that PR checkers and the daily build will try to continue using 24.0, and thus fail to apply the patch. Signed-off-by: Saikrishna Arcot <[email protected]>
38f7731
to
32e2fc6
Compare
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Saikrishna Arcot <[email protected]>
LGTM. |
The file being modified by the patch is in the slave container that's getting built, and not in the buildimage repo (or any submodules). Also, this is an already-existing patch. Considering there appear to be no issues now with the image version, I think the dirty tag won't appear. |
…c-net#19510) * Update disable-non-manylinux.patch due to pip being updated to 24.1.2. The code logic in this area has changed, resulting in patch conflicts. Signed-off-by: Saikrishna Arcot <[email protected]> * Update the pinned version for pip to explicitly point to 24.1.2 This is needed because the patch file that has been updated can only be applied to 24.1.2. However, the version pinning for 24.0 will mean that PR checkers and the daily build will try to continue using 24.0, and thus fail to apply the patch. Signed-off-by: Saikrishna Arcot <[email protected]> * Revert changes to version files, and pin pip to 24.2 Signed-off-by: Saikrishna Arcot <[email protected]> --------- Signed-off-by: Saikrishna Arcot <[email protected]>
Cherry-pick PR to 202405: #19918 |
…c-net#19510) * Update disable-non-manylinux.patch due to pip being updated to 24.1.2. The code logic in this area has changed, resulting in patch conflicts. Signed-off-by: Saikrishna Arcot <[email protected]> * Update the pinned version for pip to explicitly point to 24.1.2 This is needed because the patch file that has been updated can only be applied to 24.1.2. However, the version pinning for 24.0 will mean that PR checkers and the daily build will try to continue using 24.0, and thus fail to apply the patch. Signed-off-by: Saikrishna Arcot <[email protected]> * Revert changes to version files, and pin pip to 24.2 Signed-off-by: Saikrishna Arcot <[email protected]> --------- Signed-off-by: Saikrishna Arcot <[email protected]>
* Update disable-non-manylinux.patch due to pip being updated to 24.1.2. The code logic in this area has changed, resulting in patch conflicts. Signed-off-by: Saikrishna Arcot <[email protected]> * Update the pinned version for pip to explicitly point to 24.1.2 This is needed because the patch file that has been updated can only be applied to 24.1.2. However, the version pinning for 24.0 will mean that PR checkers and the daily build will try to continue using 24.0, and thus fail to apply the patch. Signed-off-by: Saikrishna Arcot <[email protected]> * Revert changes to version files, and pin pip to 24.2 Signed-off-by: Saikrishna Arcot <[email protected]> --------- Signed-off-by: Saikrishna Arcot <[email protected]>
@saiarcot895 , Cherry pick to 202311 and 202305 failed. Can you help create cherry pick PR? |
Hi @liushilongbuaa, I think current blocker is #20018, but this will need to be backported as well. Let me create a PR for this. |
Opened #20037 for 202311 cherry-pick, and that should be cherry-pickable to 202305, so I added the request for 202305 label. |
Why I did it
Pip has been recently updated to 24.2. For armhf, there is a patch file that gets applied to disable the use of manylinux wheels, to avoid the use of packages that might be using a newer glibc version than what is available on the system. This patch file was designed for 24.0, but can't be applied to 24.2.
Update the patch file to apply on 24.2, and make sure version 24.2 of pip gets installed.
This also fixes the version upgrade pipeline errors for master branch.
Work item tracking
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)