Skip to content
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

Merged

Conversation

saiarcot895
Copy link
Contributor

@saiarcot895 saiarcot895 commented Jul 9, 2024

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
  • Microsoft ADO (number only): 28835746

How I did it

How to verify it

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

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)

@saiarcot895 saiarcot895 requested a review from lguohan as a code owner July 9, 2024 00:26
The code logic in this area has changed, resulting in patch conflicts.

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
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 <sarcot@microsoft.com>
@saiarcot895 saiarcot895 force-pushed the fix-armhf-build-due-to-pip-update branch from 38f7731 to 32e2fc6 Compare July 9, 2024 01:12
@saiarcot895
Copy link
Contributor Author

/azpw run Azure.sonic-buildimage

@mssonicbld
Copy link
Collaborator

/AzurePipelines run Azure.sonic-buildimage

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
@saiarcot895 saiarcot895 changed the title Update disable-non-manylinux.patch due to pip being updated to 24.1.2 Pin pip to version 24.2, and update disable-non-manylinux.patch Aug 6, 2024
@liushilongbuaa
Copy link
Contributor

LGTM.
I'm not sure if this patch will make sonic_version to be 'dirty-******'. Please confirm it.

@saiarcot895
Copy link
Contributor Author

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.

@yxieca yxieca merged commit 0efc28d into sonic-net:master Aug 12, 2024
11 checks passed
@saiarcot895 saiarcot895 deleted the fix-armhf-build-due-to-pip-update branch August 12, 2024 19:23
mssonicbld pushed a commit to mssonicbld/sonic-buildimage that referenced this pull request Aug 15, 2024
…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 <sarcot@microsoft.com>

* 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 <sarcot@microsoft.com>

* Revert changes to version files, and pin pip to 24.2

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>

---------

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
@mssonicbld
Copy link
Collaborator

Cherry-pick PR to 202405: #19918

matiAlfaro pushed a commit to Marvell-switching/sonic-buildimage that referenced this pull request Aug 21, 2024
…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 <sarcot@microsoft.com>

* 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 <sarcot@microsoft.com>

* Revert changes to version files, and pin pip to 24.2

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>

---------

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
mssonicbld pushed a commit that referenced this pull request Aug 22, 2024
* 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 <sarcot@microsoft.com>

* 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 <sarcot@microsoft.com>

* Revert changes to version files, and pin pip to 24.2

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>

---------

Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
@liushilongbuaa
Copy link
Contributor

@saiarcot895 , Cherry pick to 202311 and 202305 failed. Can you help create cherry pick PR?
It blocks other pipelines.

@saiarcot895
Copy link
Contributor Author

Hi @liushilongbuaa, I think current blocker is #20018, but this will need to be backported as well. Let me create a PR for this.

@saiarcot895
Copy link
Contributor Author

Opened #20037 for 202311 cherry-pick, and that should be cherry-pickable to 202305, so I added the request for 202305 label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants