-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add a SL Micro 6.0 GA kernel module development container #2017
base: main
Are you sure you want to change the base?
Conversation
Created a staging project on OBS for 16.0: home:defolos:BCI:Staging:16.0:16.0-2017 Build ResultsRepository
Repository
Repository
Repository
Repository
Repository
Repository
Repository
Build succeeded ✅ To run BCI-tests against this PR, use the following command: OS_VERSION=16.0 TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/16.0/16.0-2017/ tox -- -n auto The following images can be pulled from the staging project:
|
372da42
to
78663b1
Compare
78663b1
to
1941568
Compare
Created a staging project on OBS for Tumbleweed: home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-2017 Build ResultsRepository
Repository
Repository
Repository
Build succeeded ✅ To run BCI-tests against this PR, use the following command: OS_VERSION=tumbleweed TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/tumbleweed/tumbleweed-2017/ tox -- -n auto The following images can be pulled from the staging project:
|
1941568
to
6f67d1b
Compare
6f67d1b
to
1e3992d
Compare
1e3992d
to
50739da
Compare
50739da
to
a9262c5
Compare
a9262c5
to
1bd67cf
Compare
1bd67cf
to
9be0c47
Compare
9be0c47
to
97f66f5
Compare
97f66f5
to
8782aec
Compare
8782aec
to
ef638c5
Compare
ef638c5
to
55bde29
Compare
Created a staging project on OBS for 6: home:defolos:BCI:Staging:SLE-15-SP6:6-2017 Build ResultsRepository
Repository
Repository
Repository
Repository
Repository
Repository
Repository
Build succeeded ✅ To run BCI-tests against this PR, use the following command: OS_VERSION=15.6 TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/sle-15-sp6/6-2017/ tox -- -n auto The following images can be pulled from the staging project:
|
Created a staging project on OBS for 5: home:defolos:BCI:Staging:SLE-15-SP5:5-2017 Build ResultsRepository
Repository
Repository
Repository
Repository
Repository
Repository
Repository
Build succeeded ✅ To run BCI-tests against this PR, use the following command: OS_VERSION=15.5 TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/sle-15-sp5/5-2017/ tox -- -n auto The following images can be pulled from the staging project:
|
Created a staging project on OBS for 7: home:defolos:BCI:Staging:SLE-15-SP7:7-2017 Build ResultsRepository
Repository
Repository
Repository
Repository
Repository
Repository
Repository
Build succeeded ✅ To run BCI-tests against this PR, use the following command: OS_VERSION=15.7 TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/sle-15-sp7/7-2017/ tox -- -n auto The following images can be pulled from the staging project:
|
55bde29
to
1edaba4
Compare
f""" | ||
{DOCKERFILE_RUN} \\ | ||
[ $(LC_ALL=C rpm --checksig -v *rpm | \\ | ||
grep -c -E "^ *V3.*key ID 09d9ea69:") = {len(_SLM60_KERNEL_PACKAGES)} ] \\ |
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.
nit: should this key number be a variable alongside _SLM60_KERNEL_PACKAGES
for future updates?
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.
It's the signing key, we're not going to change that.. but I don't care, I can make it a variable if that's wanted.
Has the kernel team agreed to this? |
the kernel team is not needed to agree to this because it pulls gcc-build not gcc. I guess your question is whether the toolchain team has agreed to it and that discussion is currently commencing. does that prevent us from merging this PR and the corresponding test suite improvements though? so far we said that jira + commitment is only needed for releasing the container, which this PR is not doing. |
No description provided.