-
Notifications
You must be signed in to change notification settings - Fork 56
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
coreos-overlay/profiles: Add keywords for arm64 sdk #2012
Conversation
@@ -27,7 +29,7 @@ | |||
=app-shells/bash-5.2_p26 ~amd64 ~arm64 | |||
|
|||
# No keyword for arm64 yet. | |||
=coreos-devel/fero-client-0.1.1 ** | |||
~coreos-devel/fero-client-0.1.1 ** |
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.
Shouldn't we just add the keyword to fero-client instead?
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, I'd say so too, it's our ebuild. On a tangent - we probably we should fork fero-client to flatcar org, because upstream is archived.
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.
Moved keyword to the ebuild and deleted this entry from the profile
sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/package.accept_keywords
Show resolved
Hide resolved
ccid-1.5.4 is marked ~arm64 but is a depdendency of the Flatcar SDK. Keyword in profile so that an arm64 SDK can be built. Signed-off-by: Jeremi Piotrowski <[email protected]>
fero-client is a dependency of the Flatcar SDK. Keyword it so that the Flatcar SDK can be built for arm64. The keyword entry from the profile can be removed, it wasn't used since the ebuild was upreved to -r1. Signed-off-by: Jeremi Piotrowski <[email protected]>
ab69bcf
to
7c03353
Compare
Add arm64 keywords for sdk packages
How to use
[ describe what reviewers need to do in order to validate this PR ]
Testing done
Testing with bootstrap_sdk when starting from dev container tarball as seed. These missing keywords show up in stage4.
[Describe the testing you have done before submitting this PR. Please include both the commands you issued as well as the output you got.]
changelog/
directory (user-facing change, bug fix, security fix, update)/boot
and/usr
size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.