-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Update SDK to 7.0.100-alpha.1.21480.20 #37192
Conversation
Fixes #37151 |
Helix seems to be stuck on RC2? Any idea where that's specified? Nevermind, I think it's here:
|
Linux build failure:
dotnet/runtime#59431 (comment) Are our linux agents old? |
New image seems to require a change to our commands:
|
Hmm, the only commas are in the description. We could always try a run-on sentence 😁. |
Maybe the command supports escaping the comma in some way❔ I'm not sure how to find the Ruby sources but I'm hoping it's more clear when looking at baseparser.rb:673, baseparser.rb:542, or baseparser.rb:515 what it's attempting to parse. |
Hmm I'm not sure it's the command, it looks more like an issue loading the ruby code. Does this image have the right version? |
It is possible to install ruby 2.5 on centos 7 though, from the |
I believe that'd require updating the dockerfile here with the ruby25 script / instantiation you suggest. This would likely involve creating and publishing a new image with those changes. Would that be possible? cc/ @dougbu ? |
We use the image to build only our two RPM projects: src/Installers/Rpm/Runtime/Rpm.Runtime.rpmproj and src/Installers/Rpm/TargetingPack/Rpm.TargetingPack.rpmproj. Most of the real work is done in src/Installers/Rpm/Directory.Build.targets. From what I can see, If we can move to CentOS 8 without breaking our RHEL 7 compatibility, I guess I'm 🆗 with it. I continue to have nagging doubts about whether the
That's not a big surprise because that image is for RHEL 7.5 and is 3 or 4 years old. We were using it until it stopped working with the OpenSSL expectations in the SDK. That's why we've been messing w/ the image in the first place. An updated RHEL 7 or CentOS 7 image containing compatible
I guess we could add this to eng/docker/rhel.Dockerfile. But, wouldn't a working and modern |
No, that wouldn't be necessary @TanayParikh. the Dockerfile is completely additive; it creates layers on top of the image we download from |
@dougbu could you summarize what the next steps are to get this merged? |
Sure @pranavkm. We're basically waiting for more information from people like @janvorli @mthalman @NikolaMilosavljevic. The options are
Looking back at this list, I lean toward (2) unless someone tells us my concerns about creating the RPM on a CentOS 8 image and running it on RHEL 7 are unfounded. |
Nice to have: Figure out why the new SDK appears to be incompatible w/ the OpenSSL version on RHEL 7.5. It may not matter because 7.5 is out of support (right @Tratcher❔) but we tend not to break things this way. |
The original runtime change is discussed in dotnet/runtime#59431 (comment), which requires features from updated versions of OpenSSL. This is a harder requirement than has been enforced in the past. |
How about we do option (b) and file an issue to mop this up based on a resolution? PR is out for a week and it'd be good to pick up SDK changes because waiting in the past has come to bite us. |
Perhaps a missing /etc/scl/conf folder @pranavkm❔
/fyi I tend to fire up |
You have accidentally removed the
in the last iteration |
RUN gem uninstall fpm | ||
RUN yum remove -y rubygems | ||
RUN yum remove -y ruby-devel | ||
RUN yum --enablerepo=centos-sclo-rh -y install rh-ruby25 | ||
RUN yum --enablerepo=centos-sclo-rh -y install rh-ruby25-ruby-devel | ||
RUN yum --enablerepo=centos-sclo-rh -y install rh-ruby25-rubygems | ||
RUN scl enable rh-ruby25 'gem install --no-document fpm' |
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 is a lot and all the more reason to move to a Docker image with matching fpm
and ruby
installations soon
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.
Yup. @janvorli helped with it. The problem was that fpm uses the ruby in the /usr/bin
dir and we had to reset enough state to be have it use the new version. Again, I'd much rather we use this as a stop-gap and merge it (assuming it works this time), than hold out for a compatible image.
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.
I completely agree on this being a stop gap. My comment amounted to "Ick, let's burn this w/ fire ASAP" 😃
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.
#37406 tracks undoing these changes.
Wahoo❕ |
Weekly SDK update.