-
Notifications
You must be signed in to change notification settings - Fork 159
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
Updating next-devel manifest for f40 #2901
Conversation
⛔ The |
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.
LGTM
though in order to get CI to pass I think you need to follow the step in coreos/fedora-coreos-tracker#1674 to update the x86_64 lockfile. |
8184a1b
to
beddba4
Compare
The manifest lockfile has been updated. |
and now CI is failing because of coreos/fedora-coreos-tracker#1694 can you just drop the addition of the candidate compose repo here and we'll add it in a followup PR. |
or actually, just go ahead and add an override to pin on the old version of shim like I did in #2904 |
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.
LGTM
ok the overrides are added. |
The kola test |
guess we'll need to add |
Let's also snooze `ext.config.var-mount.scsi-id` on next & next-devel since it's been failing on F40. Ref: coreos#2901
Let's also snooze `ext.config.var-mount.scsi-id` on next & next-devel since it's been failing on F40. Ref: coreos#2901
Let's also snooze `ext.config.var-mount.scsi-id` on next & next-devel since it's been failing on F40. Ref: #2901
The new shim-15.8-2 seems to not work for secure boot: coreos/fedora-coreos-tracker#1694
c8aee0b
to
d9a946e
Compare
Ref: coreos/fedora-coreos-tracker#1674