we _think_ so but we need to spin a new iso to test
we think so but we need to spin a new iso to test
JI'm just getting in and caffeneiting so I can work on this this morning but it'd be nice to finish and get the announcement out so we can chill this weekend
J@bsherman want me to just make the new iso?
Jor I guess anyone who can merge can
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...
Ain theory you could check the iso produced by iso selftest here: https://github.com/ublue-os/isogenerator/actions/runs/5019932152
JI'm downloading it now
AI have good ideas once in a blue moon 
NI’m a bit late but this is the tracking issue
https://github.com/fedora-silverblue/issue-tracker/issues/120
https://github.com/fedora-silverblue/issue-tracker/issues/120
Aoh before you make a new iso we need to bump the version of the isogenerator
AGitHub
I have created a release beep boop
2.0.1 (2023-05-19)
Bug Fixes
don't hardcode ublue-os on grub.cfg, use github repository name (#61) (111381f)
use new mirror for boot.iso (#66) (d7b37f0)
...![chore(main): release 2.0.1 by github-actions[bot] · Pull Request #6...](https://images-ext-2.discordapp.net/external/g6wN6ZHkW2cH6t7OXTeFFiKhH4nfUebz5AfXgfPy_Pg/https/opengraph.githubassets.com/a63ac5b76c76ab8a96a4208a6e512bbb987b87eaefaf22cd0bf8a01fdfe2a21c/ublue-os/isogenerator/pull/62)
I have created a release beep boop2.0.1 (2023-05-19)
Bug Fixes
don't hardcode ublue-os on grub.cfg, use github repository name (#61) (111381f)
use new mirror for boot.iso (#66) (d7b37f0)
...
Jok I'll need to rev a new one, new iso is done
AI can merge this and you can bump up main to 2.0.1
Jack
Jthe new key should be on this iso
Jhow do I check the key on the new iso? sorry I am totally unfamiliar with this part of linux
Amount -o loop $the_iso /some/dir and then find some file named like installer/kickstart/post-install-nvidia.shAif you find that then you can confirm if it has 2 secure boot key lines
Aand also look for
installer/securebootkeys/JI'm booted into the new image
Joh derp
Jit'd be on the nvidia image wouldn't it.
Ayeah
J-rw-r--r--. 1 root root 1550 May 19 09:20 ublue-os-nvidia-public-key.der
Jit's right in the root when I mount the ISO
Athere you go
AI think Josh copied it to a few places
AJwell I hope it wasn't josh because we need the key bsherman added.
DI figured out how to build nix from source https://nixos.org/manual/nix/unstable/contributing/hacking.html
AJosh added the code to copy the keys around iirc 
Jdo you know what command to run to check the key?
Asadly no, check
mokutil --helpAI have meetings at work, I'll try to check if I get some time
Jyeah this is way out of my scope, I'll stand by
PYeah I've been meaning to try that at some point
JI'll PR the version bump in the meantime
Ait looks like you need nix?
PI haven't tried it but I get the sense that the use of nix there is to make sure you have all the dependencies needed, and that it'd probably work without nix as long as you have those dependencies (at least it looks like it's doing normal autotools things)
Apackage it for fedora upstream
Adnf install -y nix
Dthat would be so fricken nice. but I don't know much about packaging. I figured how to build it from source with a custom prefix which is a huge advancement.
Aif you can figure out how to build it in fedora without having to install nix beforehand that'd be a good first step
Abasically see what dependencies it needs to the autotools configure will succeed
Dthat is gonna be hard. I could compile it then have it in a tar for installation
Athere's two hard parts to packaging:
1. figuring out dependencies (some of them may not even be in fedora yet!)
2. figuring out what files the program needs after install
1. figuring out dependencies (some of them may not even be in fedora yet!)
2. figuring out what files the program needs after install
DI think all the dependencies in the compiled nix is already there
Ayeah otherwise it would not work
Abut if you are installing nix to build nix, why not just ship the installed version and skip the compilation step?
Dthat is what I'm planning to do
Dwhat do you think the best prefix would be?
/opt/nix-usr /usr/local or something else?