Sherman had to change it because the one I put apparently just died
Sherman had to change it because the one I put apparently just died
Jdid you see the fcix mirror thing? I wish rpmfusion was on it, heh
Jok restarting the last job
AI wonder if there's a way of straight up hosting an rpm repo on github 
Awe could mirror both Fedora and RPMFusion lol
Jwe mulled using github pages
Jbut considering it's taken us like a week to rotate a key out I'm not so keen on new complexity
Ayeah I think such project would be outside of the scope of ublue
Joh derp
JGitHub
Jorge regenerated the new akmods key to include meaningful CN, "ublue akmods", instead of the default "akmods local singing CA".
For #100
For #100
Abut it'd be kinda really useful for fedora at large... free mirrors lol
Jwe needed this
Ait is removing something
JI think that's the old key right?
Jok well he wanted this done so doing it
AGitHub
* chore: add new public key for akmods (#212)
Adds the new public_key.der which will be used for signing akmods in the
future, making it available in the new path today. This will allow users
to s...
Adds the new public_key.der which will be used for signing akmods in the
future, making it available in the new path today. This will allow users
to s...
Ahe added that file here
Aand the PR you sent is removing the file
Ait seems that it would break things?
Jalright I won't merge it then
Joh we're replacing the old key
Jok I'm merging it, it can't be any more broken than it already is
Jthen I'll make a new release with this + the updated action
Xgreat, thanks!
BYes. That’s cool with me
I dunno if you saw the last error I had. It was a lack of root privileges in CI. I wondered how that ever worked
I dunno if you saw the last error I had. It was a lack of root privileges in CI. I wondered how that ever worked
BI think I was wrong about the mirror dying. I didn’t realize the “releases” path part was parameterized and could be replaced with developement. The latter directory seems to have disappeared on several mirrors
Jyeah it's only open when they branch I think
J@bsherman ok when you're back, I think everything is in place, ready to gen a new ISO
Bi'm here 
Band yeah, so in isogenerator, that's what eventually got it to TRY buidling an ISO, yeah, i changed the mirror, but it was really changing the params to "realeases" that made it go further
Bso... what's next exactlY?
Jwell I made a new ISO this morning
Jbut I don't know how to check the key
Jbut that was before we merged #102
Byes, this is what i want to help test so we know exactly what to expect on a new install
Jok so do you want to try with the iso from this morning or make you a fresh one?
Boh, i guess it was just waiting on an approve 
Bi think your new iso should be fine, it just needed the keys on the ISO for the secureboot mokutil import
Bwhere's ISO> i'll test too
Bi setup a machine for this test LOL 
JGitHub
1.4.0 (2023-05-17)
Features
add adw-gtk3-theme for Silverblue (#204) (3aa1345)
add kernel-tools (#208) (b2d0b07)
add openrgb udev rules (#197) (a95ec2d)
add podman-compose (#180) (4eea999)
add tmu...
Features
add adw-gtk3-theme for Silverblue (#204) (3aa1345)
add kernel-tools (#208) (b2d0b07)
add openrgb udev rules (#197) (a95ec2d)
add podman-compose (#180) (4eea999)
add tmu...
Jprereleased so if you ack it we'll just roll up and do 1.4.1 with akdev's updates
JI need to start on the draft announcement
Bi tried to read up but missed the specific updates from akdev
Jjust some minor PRs in isogenerator
DI got a different idea, /opt/nix-usr will have binareis, manuals, and a feel other things linked to /usr/local for easier tar extracting
Bok, asking because i don't see commits/pr from akdev in last several hours, no sweat, just curious
i'll move forward with testing ISO now
i'll move forward with testing ISO now
J
AI just merged the release PR for isogenerator so it would generate a new release tag
Bcool, thank you. i was just curious
Bsweet tool!
