Bexplain pls?
KGitHub
Since we use differing kernels from upstream, we should be properly setting the ostree.linux label on the image to reflect the actual kernel within the image.
Bi see
Bi replied
KI'll make an issue in main 
DMain adds the rpmfusion repo in install.sh right? And then that gets used to install Nvidia in hwe?
DSo we need to add negativo17's Nvidia repo in hwe since that one isn't in main ,right?
BFirst thing i thought of is the Space Force. So I guess you're doing it right?
DIs my understanding correct that something like this would be what we need for the negativo17 driver? https://github.com/ublue-os/hwe/pull/229
MTake a look at ucore, Bazzite, and bluefin. Each uses the repo for some items. You'll see what we mean that it's a little bit more complicated than just pulling in the repo
Bif you want to work on things... I suggest you clone/fork repos and see if you can get something building in your account ... then you can PR something you have confidence in
DThat's a good idea actually
Band yes, as @M2 said... it's more than a repo... nvidia is probably the single most complex "feature" in all of ublue... we've had multiple versions of the driver building in akmods repo, plus we pre-install those different versions in
*-nvidia images in hwe repo, and also install related things like support repos, CUDA support for containers, etc.Bthe only other single feature which is close is custom kernels (asus/fsync/surface)
Bso i honestly wouldn't suggest starting there
DAh, I see. Having the version in the image tags is going to be tough in all of the downstream images
DSo basically it needs a PR in every repo and a coordinated effort to change that
BBGitHub
This will merge when it builds cleanly, after rpmfusion migrates the new package from updates-testing to updates repo.
This will be apparent when:
this builds
v4l2loopback is present here: https:/...
This will be apparent when:
this builds
v4l2loopback is present here: https:/...
Lhi 
been using bluefin-dx-40 prerelease for a while now, noticed today that devpod was temporarily removed. is it easiest to rebase back to 39 to get it back ?
been using bluefin-dx-40 prerelease for a while now, noticed today that devpod was temporarily removed. is it easiest to rebase back to 39 to get it back ?
Lok. thank you
NDevpod will soon be readded but right now it has some issues while building the image. If you want to stay on :40 you could try the AppImage for now. https://devpod.sh/docs/getting-started/install
In order to get started with DevPod, you can choose between the DevPod Desktop application and DevPod CLI.
J@RoyalOughtness you're going to need to kick off some rebuilds
J@xyny @fiftydinar ditto people with custom images.
Jmain's being rebuilt right now and after that we'll do the others,
B@Robert (p5) any specific reason 38 is building manually?
ROh shit. Did Timothee's CVE not affect 38?
Bit didn't
RSorry!
Bit's fine... i only build 39/40 manually so i could start confirming they were fixed sooner than later
Bi've confirmed the fix is good in F39
B
RAh, I was on mobile, saw "38" was affected but didn't notice it was only CoreOS, and 39+ desktop images
Bi'm torn on what to do, but i think i'd prefer to let the scheduled builds run for main and then we can manually build hwe / bluefin / bazzite
B
Bi'm trying not to say anything which could jinx us LOL
B@j0rge we talked about tightening up the cron timers the other day i can see we have not yet done so on main
i can see we have not yet done so on main Bwe're still waiting for F38
Bbut, maybe since @p5 just built it, we skip.
@Robert (p5) wanna push "build now" on hwe 39 and 40?
@Robert (p5) wanna push "build now" on hwe 39 and 40?
RLooking at yesterday's runs, HWE should be building in about 30 minutes anyway?
NI'm starting a thread.
NPutting out the announcement now.
Xthanks for the heads-up
J@Noel everything we need is queued up, you may indulge yourself on the builders.
NI'm going to gorge myself on builders. ALL MINE!
Byou didn't ask me if i needed builders for ucore
B
