Kas soon as prompt has a stable release I can MR it
Ksince none of this stuff points to the .Devel namespace
ZIm excited!
A@EyeCantCU still feeling a bit weak so might have to postpone the work until tomorrow 
ESorry to hear that, but sounds good. I'll have a look over things today to get an idea of what would need to be done. Hope you start feeling better
AWe need to do the following:
1. Modify this guy to have a flatpak ref/flatpak apps as input parameter: https://github.com/ublue-os/lorax-compose/blob/main/action.yml
2. Modify this guy to add the Lorax template for flatpaks: https://github.com/ublue-os/lorax-compose/blob/main/mkociso
3. Wire the inputs from the action into the Lorax template
1. Modify this guy to have a flatpak ref/flatpak apps as input parameter: https://github.com/ublue-os/lorax-compose/blob/main/action.yml
2. Modify this guy to add the Lorax template for flatpaks: https://github.com/ublue-os/lorax-compose/blob/main/mkociso
3. Wire the inputs from the action into the Lorax template
GitHub
Contribute to ublue-os/lorax-compose development by creating an account on GitHub.
ESweet! I'll get to work on that after lunch! Thank you so much
B@EyeCantCU @akdev I’ve been only partially keeping up with the flatpak on image stuff. What’s the TL;DR? Do we just want to prove it can be done? Is it all about shipping Prompt pre-release?
K
ANo, it’s just the same way fedora SB does it
AI don’t know what Bazzite wants to ship but in general just seems like missing functionality we have been putting onto yafti
Kwould love to use whatever upstream does eventually
FIn yafti & default-flatpaks module
This is something I'm excited about
This is something I'm excited about
Kfor now our flatpak manager works
BAh, cool. You figured out how they do it so we can pre bundle a few desired flatpaks which will still be removable/upgradable by a user?
That’s pretty cool!
That’s pretty cool!
Kit'll retry until everything in the list is installed
Kso that's all we need
AYeah
EEven after installer support is there, I think the flatpak manager will certainly still be useful. Especially for people that rebase to the image
E@akdev I think this handles 1 & 2. Looking into 3
https://github.com/EyeCantCU/lorax-compose/commit/b95263cb6c492cdb307b7ef26348b0780e78d6c7
https://github.com/EyeCantCU/lorax-compose/commit/b95263cb6c492cdb307b7ef26348b0780e78d6c7
FIt would be nice to contribute this to startingpoint once it's done
AThat looks right, maybe it should be an option that can be specified multiple times?
ECan certainly look into that
JYES!!!!!!
B@j0rge @Marco could one of you make the blincus repo public please?
Jall set
Mdone
Mwell that explains the error of "already public"
J
JGitHub
Github Action to automatically update digests for container images. - GitHub - chainguard-dev/digestabot: Github Action to automatically update digests for container images.
Jfyi ya'll
K@j0rge PR open if you want to take a look
KFor bluefin
JI see it, q: how do we ensure the logo menu is always on the left? the order of things in the panel is black magic to me
JI'd also like to heads-up folks on the forums on the change, but I can work on that after the conference tonite
Jdo we know what happens to existing users? like will my ctrl-alt-t change? I think this would just deal with new installs right?
Jooh dang are the upstream silverblue updates still busted? dang.
KIt's based on a priority, I've never had it anywhere but the far left
KWhatever you experienced must have been a bug
Jack
KI'm not sure on existing keyboard shortcuts, need to look into that
JI've not had a bug with it, I was wondering, I had a different bug but that was with an older version
JI'm mulling if we need a :testing like bazzite has but also I'm like, not wanting to deal with that lol
J@KyleGospo which copr is logomenu in?
KStaging
KSame with the Nautilus extension
KAnd I'm open to submitting those for upstream packaging
Jnice.
KHappy to be maintainer there
Jwe doing 38 too or just 39?
