-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Stop using devtoolset-2 to provide GCC4.8 #2339
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Stewart X Addison <[email protected]>
sxa
force-pushed
the
remove_devtoolset_2
branch
from
October 5, 2021 17:35
6422859
to
ebbcc4b
Compare
Looks like the
|
Signed-off-by: Stewart X Addison <[email protected]>
Signed-off-by: Stewart X Addison <[email protected]>
sxa
force-pushed
the
remove_devtoolset_2
branch
from
October 5, 2021 22:24
658e291
to
c47786f
Compare
sxa
force-pushed
the
remove_devtoolset_2
branch
from
October 5, 2021 22:42
c47786f
to
f5f368b
Compare
Signed-off-by: Stewart X Addison <[email protected]>
sxa
force-pushed
the
remove_devtoolset_2
branch
from
October 6, 2021 08:22
4cdcb76
to
09b4a89
Compare
Signed-off-by: Stewart X Addison <[email protected]>
Signed-off-by: Stewart X Addison <[email protected]>
sxa
force-pushed
the
remove_devtoolset_2
branch
from
October 7, 2021 15:22
b2f014d
to
128bdf7
Compare
3 tasks
Superceded by #2344 in order to resolve the certificate problem, but we should considere whether we still need GCC4.8 on the machines going forward. |
Closing as #2344 was ultimatley a preferable solution here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DRAFT as I don't necessarily want to merge this, but I want to see if it unblocks the playbook execution on CentOS6 (Let's Encrypt failure from people.centos.com)
I don't think 4.8 is needed any more for any releases, as the lines that used it (JDK8/J9/s390x) are superceded by later directives in build.sh
Signed-off-by: Stewart X Addison [email protected]
Checklist