Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

[release/3.1] backports dotnet#67763: fix build with musl 1.2.3 #28245

Closed
wants to merge 1 commit into from

Conversation

ayakael
Copy link

@ayakael ayakael commented Apr 25, 2022

Backports dotnet/runtime#67772 to release/3.1 to fix build with musl 1.2.3

@ayakael
Copy link
Author

ayakael commented Apr 25, 2022

@nekopsykose I see that you backported the musl 123 fix on Alpine's side. (thanks for that!) You removed whatever modifications in src/pal/src/init/pal.cpp. Why was that? Could this be the source of the failing tests on release/3.1 and release/5.0?

@nekopsykose
Copy link

afaik those don't change any semantics (NULL == nullptr), it just failed to apply cleanly and i was lazy for a mere backport :)

@ayakael
Copy link
Author

ayakael commented Apr 25, 2022

afaik those don't change any semantics (NULL == nullptr), it just failed to apply cleanly and i was lazy for a mere backport :)

Gotcha, then for the upgrade to 3.1.418 I'll apply proper change - it's what upstream wants.

@ayakael
Copy link
Author

ayakael commented Apr 25, 2022

Confirmed good build in Alpine pipelines

@carlossanlop
Copy link
Member

@ayakael is this ready to merge? Can you get a sign-off from someone in your team?

@carlossanlop
Copy link
Member

Ah, it's missing the servicing consider label. I added it. This needs to go through tactics.

@carlossanlop carlossanlop added the Servicing-consider Issue for next servicing release review label May 3, 2022
@jeffschwMSFT jeffschwMSFT requested a review from gbalykov May 12, 2022 17:03
@jeffschwMSFT
Copy link
Member

@janvorli can you do a code review? Same as dotnet/runtime#67772

@jeffschwMSFT jeffschwMSFT requested a review from janvorli May 12, 2022 17:08
@JulieLeeMSFT JulieLeeMSFT added this to the 3.1.x milestone May 12, 2022
@JulieLeeMSFT
Copy link
Member

@ayakael, could you update the PR body with a template we use to get servicing approval? Once I get it from you, I will get an approval. Please refer an example from dotnet/runtime#68934 which includes:

  • What is the issue
  • What was the root cuase
  • What was the fix
  • Customer Impact
  • Testing
  • Risk (if it is low, why is it low?)

@JulieLeeMSFT JulieLeeMSFT removed the Servicing-consider Issue for next servicing release review label May 13, 2022
@JulieLeeMSFT
Copy link
Member

Removing servicing consider until I hear back from @ayakael and get code review from @janvorli.
cc @mangod9.

@JulieLeeMSFT
Copy link
Member

@ayakael, I have a question to you. You put up servicing PRs for only .NET 3.1 and .NET 5. I don't see .NET 6 patch. What is your plan for .NET 6 patch?

When fixing issues, we need to fix all the supported releases between the lowest needed (in this case .NET 3.1) and the currently supported release (.NET 6).
Since .NET 5 is going out of support, we will need to patch both .NET 3.1 and .NET 6 if you need to patch .NET 3.1.

@carlossanlop
Copy link
Member

@ayakael the PR has been inactive for a few months. I'll close it. Feel free to reopen if you can answer the questions above.

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

Successfully merging this pull request may close these issues.

6 participants