JI see some green!
Jcrushed
Jthe reds are flakes, those can be rebuilt
Kit's a jiff what can you do
Jbut looks like we're close?
J@EyeCantCU ok merging and building in main now
Jenough greens passed. 
EAnd none are due to the kernel signer 
EDo we need to land the signer in main?
KIf this fixes it, yea
KWorth doing
EI'll update after images push and see. Getting close to my EOD anyway (not that that actually exists)
E(and not that I mind one bit that it doesn't)
Jjust waiting on bluefin-dx and I can test
EAurora DX is up, trying now. I guess it's a good thing I don't reboot often ha. Would've been a suprise this morning
Jno joy here
Jbbiab
Jmaybe we should just pin to the the last kernel, and then just bite the bullet and pin to the coreos kernel
Jwas hoping to do this eventually, not under a knife, heh
EI'm still not 100% sure what happened
EFeels odd for Fedora to introduce something so breaking mid release
Jthis happens every time, it's usually not so catastrophic though
KWorth keeping the signing regardless
KOdd that fsync isn't affected
KBeen on 6.9 for days
KShould we just pin the upstream of main for a few days?
JYeah imo
JLet's get out from under the guillotine
JThe work around instructions I linked to in the forum post are surgery, better to keep people on the older kernel
EWorking on my end
JYou have secure boot on?
EYup
J@Marc can you update and test
Aupdating right now and can give feedback too
JLaptop is in my bag will retest
JYeah the more the merrier please
ZSame error
ZNow I cannot get onto my machine, I forgot to pin
ZI've now got 2 bad deployments
ZBoys with secure not off
KYou can disable secure boot in bios to get back in
Z*boots
RI'll test shortly
EI'm guessing it's probably something different in that case? Maybe it only impacts some systems?
JA few fedora silver blue reports upstream
JBut we're also 24h behind them
JIf someone wants to update the forum post there's at least one person there
Afixed for me i think
KLooks good, in that case
