lol, anyways, the installation is different from upstream fedora
lol, anyways, the installation is different from upstream fedora
Awe have an iso lets goooooo
Aonly ones with an iso
Xthere could be another link under fedora for ublue image
Xpop has an iso
Athird party
Athey beat us to it
Abut we could have beat them by a few hours
RAnobody knows that
Aits like the old saying
Aif you didnt post an instagram story did you really go there
Ai wish i could say that having a ISO is a huge differential, but for most early adopters this don't matter a lot, and like i don't think our experience would be something that early adopters would like since they would say ugh immutable. could be wrong tough
SHow is it different? Surely it would just be added as another layered package going by the Fedora-Silverblue instructions?
RIt's pretty much the same.
- Add COPR repo
- Install cosmic-desktop package
- Enable cosmic-greeter service
SThat's what I thought
Ayou know how hard it is to build an ISO
Atook nobara 4 months to build a f40 iso
Aor sth
Athats a competitive advantage right there
Ayou cant believe how huge it is to be able to just press a button and get an iso with 0 drift
Xi mean that to install cosmic with ublue you install the image, and don't have to go through the manual steps
SAhh right, i thought you meant like it said in the instructions page. I think I just got muddled with the linking that page and ISO talk 
J@Robert (p5) PR looks good, waiting on builders, you'll need to steal this from the bluefin repo for the readme: https://github.com/ublue-os/bluefin?tab=readme-ov-file#secure-boot
Jthe public key is in the akmods repo, that's what the link points to, that should be all you need for secure boot
RThanks!
Jready to ack
RThink it's good to go.
Removed the SELinux hack and added the SecureBoot info to README
Renamed the cosmic-base image to cosmic
Updated the secureboot password to match the rest of the org
Removed the SELinux hack and added the SecureBoot info to README
Renamed the cosmic-base image to cosmic
Updated the secureboot password to match the rest of the org
A@Kyle Gospo current /usr/etc files from 30 image
message.txt2.06KB
Ajuly 30 that is
Awow thats quite a bit
Ayou really put everything in there
FIdeally, when inspecting,
/usr/etc/ should be empty, right
Jack I'll ack and merge as soon as things turn green
Ai mean rn it just gets force merged to etc
JAand the polkit.d dir that is problematic gets permission quirked afterwards
Aso the polkits should still work
Abut yeah all those dirs will have their permissions reset, so if there is a dir in those that needs special handling like polkit.d it needs to be fixed up afterwards
Kshould all be fixed in latest on bazz
Konly remaining file in /usr/etc I'm aware of is the policy.json
Astable?
Knext build, yea
Ais it in testing?
Kyes
Aok let me do testing
Kwhich is rebuilding now
Kwould re-run after that
Ayou can also switch to 0.8.3 rechunk
Ksince that gets the changes to main too
Awhich will show the tree
