ok so am I uploading a new key to this isogenerator dir?
ok so am I uploading a new key to this isogenerator dir?
Jwhat should I call it, I'm assuming I put it alongside the existing key?
Bno
Bi'm making a PR now
Bwe also need to modify script
B@j0rge so the gotcha on adding the second key the ISO
it'll be importing 2 keys, so we need to update docs to say when the user imports keys in the ugly UEFI MOK utility, they'll have to approve importing 2 keys
it'll be importing 2 keys, so we need to update docs to say when the user imports keys in the ugly UEFI MOK utility, they'll have to approve importing 2 keys
Bi should probably wipe my keys and test this
Junderstood, standing by
Bwho knew this "move a key to org secrets" was such a PITA 
Jplay nvidia games, win nvidia prizes
Bok, i just scrounged parts and built an nvidia machine... lets see if it boots
B@j0rge ok, what do you think about this PR goes into iso generator and we try to rig up pre-release build somehow, can we do that?
Jez
Bthen i can test that on my franken-vidia box
BJwe're set to normal release not prerelease ootb tho
Jdone with the perms
Bthanks guess we missed that one
Jyeah we need to move to groups, etc.
Clol
Bi know it' s not pretty but i think this is all we need https://github.com/ublue-os/isogenerator/pull/65/files
Bi really want to just run this locally to generate an ISO before we even merge that
Junderstood
Bi'm just trying to see HOW
Jwe could generate it in experimental
Boh! ok, i've not used experimental
Bbut that sounds good
Btty easier for this?
Jsec
B30 seconds here
Jno branch rules in the repo
Jso I would just copy and paste the build action that calls the iso generator and make a release
Joh it's up to date already
JI wonder if we can just hit the button
Bi'm confused
Jwe can generate an iso from this repo to test
Bok, so we need to merge isogenerator first?
Jyeah or call a specific revision in the action, which is probably what you want
Bok, ready to merge and we'll ahve experimental call it
Jwe can merge it, all we need to do is not make a release from main/nvidia which is an explicit process anyway
Bmain's use of isogenerator is tagged to v2.0.0
Jperfect, I love when we're like "oh nice work person who thought of that!"
Jinvesting in our future selves!
Jok
Bisgenerator is doing a pretty serious test
Jyeah so experimental is nice because we don't check anything, you can just merge right to main, so it's awesome for testing actions and things that would need review, etc.
Bfree to explain this to me?
Bthe isogenerator action... does it need a release to be available for experimental to use?
Bah, no, it's using main... so... i hope that means @main branch
https://github.com/ublue-os/experimental/blob/fc656e7de84f09072f00030bf91ce648028c8bfc/.github/workflows/release-please.yml#L31
https://github.com/ublue-os/experimental/blob/fc656e7de84f09072f00030bf91ce648028c8bfc/.github/workflows/release-please.yml#L31
Bso... I deleted
but looks like it skipped ISO generation
https://github.com/ublue-os/experimental/actions/runs/5019784688/jobs/9000641600
test3.md to generate a build in experimental...but looks like it skipped ISO generation
https://github.com/ublue-os/experimental/actions/runs/5019784688/jobs/9000641600
B