Tim guessing is a reference implementation?
LI've been following that XDG Default Terminal spec for a while now and it looked great last time I checked. Hopefully it gets adopted by the DEs
JFedora Discussion
As of Fedora Rawhide ~2024.01.18, I can’t rebase back to Fedora 41. I don’t have a Fedora 41 deployment to fix that. ❯ journalctl -b -1 -u ostree-finalize-staged.service Jan 21 13:11:15 abc123321bca systemd[1]: Finished ostree-finalize-staged.service - OSTree Finalize Staged Deployment. Jan 21 13:11:37 abc123321bca systemd[1]: Stopping os...
Jso I guess with composefs it means that the upgrade to 42 is a one way trip?
Plooks like it is more related to sbin and bin merge, or is that somehow related to composefs?
JI have another one
Pone way ticket then, i guess?
Joh nevermind it's the same one
Jjust in the bluefin repo
Pyeah is the same one
PI got that link from this issue
Jnod
JI think we should just put guards in the rebase helper
J
JBazzite is soundly defeating Bluefin in the year long statisitcs, though I'm winning in the 30d.
FHere's a good comment I remembered back when I was starting to use Ublue about
https://github.com/ublue-os/main/issues/211#issuecomment-1551600704
xdg-terminal-exechttps://github.com/ublue-os/main/issues/211#issuecomment-1551600704
FBazzite already uses the "better alternative" & it works well
Foh, Bluefin uses it too, so you're all set
R@M2 please could you approve this PR
https://github.com/ublue-os/hwe/pull/326
Enables Nvidia builds for F42
https://github.com/ublue-os/hwe/pull/326
Enables Nvidia builds for F42
GitHub
Adds a build for Fedora 42. I'm not super familiar with the tag lifecycle, but I think I've got them correct. 42 is latest and beta, 41 is stable and 40 is gts.
Mrechunk works inside of a podman unshare environment
Tfancy!
Tman i wish we could use the rpm-ostree rechunker
Acould someone with write access please review/merge this PR? https://github.com/ublue-os/yafti/pull/328
I know yafti is being phased out but secureblue still uses it and this is the last blocker for secureblue's upgrade to F42
I know yafti is being phased out but secureblue still uses it and this is the last blocker for secureblue's upgrade to F42
GitHub
According to the documentation, GBulb is unnecessary and non-functional with recent versions of PyGObject. I removed GBulb, bumped the minimum required version of PyGObject to 3.50.0, and modified ...
ZAbout that, I thought of something really dumb. Can we rechunk, but instead of relying on rpm-ostree, doing it manually with containerfiles
COPY?
ANo, you'd need to fork buildah
AI built rechunk I thought about that
ZIsn't rechunking just copying package related files into a layer?
AYou can't do dynamic copy instructions
ZOh you can with dagger
AYou can't ensure the layer has the correct file order
Jall set!
ZFile order?
AAnd fix the timestamps
AYes
AIn order for a layer to have the same hash you need the same tar atream
AThe only tool that can create custom tar streams is ostree RS ext
ZCould someone in theory do the same with just the tar command?
ACould you in theory rebuild ostree RS ext?
AYes
ABut it exists already so
ZYeah but it depends on buildah I'm assuming
ANo
AOstree RS ext builds tar streams manually
ZMmm ideally I would get rid of ostree dependency completely on CI
AThen you eat that on deployment
AEither you make the commit or the client does and it explodes
RHonestly, I'd wait and see how things pan out with composefs.
This will remove ostree dependency throughout the entire stack
This will remove ostree dependency throughout the entire stack
ZWell yeah, still need to figure out how to do rechunking
AOstree is still the backend and there is no proposed replacement
AThey're just trying to obfuscate it
