-
Notifications
You must be signed in to change notification settings - Fork 287
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
ruby 3.4: interpreter & gem batch 1 #36408
ruby 3.4: interpreter & gem batch 1 #36408
Conversation
42a275d
to
40a255f
Compare
40a255f
to
c6d5581
Compare
c6d5581
to
6aee559
Compare
6aee559
to
2cfd197
Compare
2cfd197
to
629f0cd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks.
If you want to see the actual diff from the 3.3 copy you can look at justinvreeland@21c0c0d |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will need a force merge, since this many files makes ci-sbom-validity
time out and die.
This was created by renaming the 3.3 file to 3.4.
Turning the gemspec patches into files. See https://github.com/wolfi-dev/os/blob/main/ruby3.2-bouncy-castle-java/0001-add-gemspec.patch
Providing the base64, csv, and drb package from the main ruby package because they now conflict and some packages have implicit dependencies on them. Which means we either need to spot update failing packages or provide it from the interpreter that is already installing these gems.