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.
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
DAOS-16621 build: Fix Go versions in rpm/deb packaging #15174
DAOS-16621 build: Fix Go versions in rpm/deb packaging #15174
Changes from 6 commits
a237458
f17c1d5
2942650
408e2d4
2b4106c
95f6cd3
b1ee4cf
11ac499
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 59 in site_scons/site_tools/go_builder.py
GitHub Actions / Pylint check
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'm not familiar with go, what does this part of the change do?
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 basically like a
requirements.txt
file in python, specifies package versions to be pulled in when installing into a golang environment (usually installed into user home directory). I'm guessing the removal of 1.22.3 was just to relax requirements as 1.22 not available on all distributions.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.
Yeah, the go mod tools added that line automatically, but I don't think we need it. It seems that it's only relevant if we want to use a different toolchain version than the minimum go version.
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 thought I'd made a comment on this change but I can't see it anywhere, apologies if I'm repeating myself here.
One of the intentions of these scripts is that an admin should be able to call them to install required packages and to do so safely, so therefore they install packages without the -y option for example. The package manager/repo configuration is all done in the dockerfile/helper scripts and this script then just installs the named packages.
This code breaks that model so the script will re-configure the node as well as install code and in addition it's also possibly not idempotent any more.
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 tested moving the Dockerfile Ubuntu version forward to 24.04 LTS and ran into a warning with the interception library (src/client/dfuse/il), I think due to an upgraded version of gcc.
I think pushing up the Ubuntu version is out of scope for this task, given that it'll require production code changes.
I could shift the PPA addition to the Dockerfile if that would be an acceptable compromise.
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.
If there's build errors then we definitely should update, that's what we're looking for with this test. Outside the scope of this PR though but I'll file a ticket and take it on.