Bis it?
EIt can't pull in the proper version
EAt least over in Nvidia
EI think the images are mismatched with what's in the Fedora repos rn
Bwell nvidia fails are expected by me, since main is failing too
BGitHub
OCI base images of Fedora with batteries included. Contribute to ublue-os/main development by creating an account on GitHub.
Blike why is kernel-uki-virt 6.4.15 here, but we should be on 6.5.5
Bsame with xpadneo
Bit's like it started running before our akmods images published?
EThis probably explains why I've been having so many build issues the last two days. That would explain it
Byeah, i let it go yesterday because 1) i was busy 2) it can happen
Bbut 2 days in a row is more concerning 
EWe may need to push back mains cron job
Bhmmm no
Bakmods finished at 6:15am GMT... and main didn't start until 7:05am GMT or so
BOH!
Bi know
EYeah, I don't think akmods is holding it back after looking more into it
Bi changed the tagging in akmods and we forgot to make main use the new tagging
EOooooof
EThat explains it
Binstead of simple ":38" it's now ":main-38" becasue of the kernel flavor
Btell me now if that's horrible
Bi did it on purpose, and it was approved but it was one of those things I expected to have a discussion about, but it was approved without discussion
but it was one of those things I expected to have a discussion about, but it was approved without discussionEI like that it's using the base name. I don't like that it breaks downstream. We should check for main as the base and use the old tagging for main akmods
Bmy reasoning was to get away from the idea that akmods was one-size-fits-all ... we'd not have a "default" that was just a version
BIf that means you wont get updates when your system is on silverblue-main:38 then its bad. otherwise ignore me
EThat's true..
Bwell it won't break downstream 
if we make a simple change in main
if we make a simple change in mainEIt should not impact that
Bit'll be fine this is exactly what we are trying to fix now
this is exactly what we are trying to fix now
EThat's true. Either way I'm fine
Bi don't like the word "main" it's so overloaded
EIt also looks like we have unanimous approval to remove kmods from 39 so I'll work on that
EIt definitely is
Jremmember when we made a
base-base?Bok, so either in
or... we change the tag
AND update the akmods README (which desperately needs it, i've got 3 open issues to update parts of it)
I think as long as it's documented in README we can made the change
akmodsor... we change the tag
mainAND update the akmods README (which desperately needs it, i've got 3 open issues to update parts of it)
I think as long as it's documented in README we can made the change
Jjust turn-up-the base-baseBmy reason for explicitly using
:main-38 instead of just :38 is to make it more clear for anyone that they can't just assume the kernel by tagsBso i think i'm going to stick to my guns there
Bfix incoming on
then i'll update some
mainthen i'll update some
akmodsIf it's as simple as the second, let's do that
Bthere's actually a PR needed for nvidia, too... doing that, but it shouldn't build until after main does
