29 Replies
is it?
It can't pull in the proper version
At least over in Nvidia
I think the images are mismatched with what's in the Fedora repos rn
well nvidia fails are expected by me, since main is failing too
GitHub
build-ublue · ublue-os/main@b9b3095
OCI base images of Fedora with batteries included. Contribute to ublue-os/main development by creating an account on GitHub.
like why is kernel-uki-virt 6.4.15 here, but we should be on 6.5.5
same with xpadneo
it's like it started running before our akmods images published?
This probably explains why I've been having so many build issues the last two days. That would explain it
yeah, i let it go yesterday because 1) i was busy 2) it can happen
but 2 days in a row is more concerning 😄
We may need to push back mains cron job
hmmm no
akmods finished at 6:15am GMT... and main didn't start until 7:05am GMT or so
OH!
i know 😄
Yeah, I don't think akmods is holding it back after looking more into it
i changed the tagging in akmods and we forgot to make main use the new tagging
Oooooof
That explains it
instead of simple ":38" it's now ":main-38" becasue of the kernel flavor
tell me now if that's horrible
i 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
I 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
my 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
If that means you wont get updates when your system is on silverblue-main:38 then its bad. otherwise ignore me
That's true..
well it won't break downstream 🙂 if we make a simple change in main
It should not impact that
it'll be fine 🙂 this is exactly what we are trying to fix now
That's true. Either way I'm fine
i don't like the word "main" it's so overloaded
It also looks like we have unanimous approval to remove kmods from 39 so I'll work on that
It definitely is
remmember when we made a
base-base?ok, so either in
akmods repo we have a little annoying logic to set the tag name to ":RELEASE" intead of ":KERNEL_FLAVOR-RELEASE" when KERNEL_FLAVOR=main
or... we change the tag main consumes...
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 changejust turn-up-the base-basemy 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 tags
so i think i'm going to stick to my guns there
fix incoming on main repo to use new tag...
then i'll update some akmods README stuffIf it's as simple as the second, let's do that
there's actually a PR needed for nvidia, too... doing that, but it shouldn't build until after main does