It appears that all of the config rpms are already installed
It appears that all of the config rpms are already installed
M
KSigning is the one with that file
Myeah, but they were saying udev rules weren't there as well
IWe were wrong. It turned out that the udev rules are present. The build fails because of a missing policy.json file. Current ublue-os:config has a commit that fixes thew issue. The cosmic image does not seem to have this commit included atm.
IState few hours ago. We are waiting on a rebuild of the cosmic image
J
Ithank you. The base image errored out at the uploading step. Can you rebuild it again, please?
Jyep, watching it
M@antheas another error with rechunk popped up this time with ucore
https://github.com/m2Giles/m2os/actions/runs/10335823416/job/28610865502#step:18:615
https://github.com/m2Giles/m2os/actions/runs/10335823416/job/28610865502#step:18:615
MThere is no previous image for that image.
MThink I figured out the cause. You put GCC in the same layer and it's not on image yet
MNope not it.
Mlooks like its gcc just failing to install correctly
Mokay. I'm guessing its somehow having a mixed subpackages of gcc causing the issue
IWe were able to fix our issue. /etc/ instead of /usr/etc/ in a script and it builds. I am uncertain if this change was introduced with rechunks. Thx
ALatest ver woes I think
AActually dunno
ACan't see the error from my phone I'll look at it in a bit
Aill look into it
Apulled the image and i get the error
AGitHub
Fixes a bug in the prefill algorithm that caused some packages to not be allocated and a subsequent crash. In addition, makes it so if this happens again due to a different bug an error is emitted ...
Aid suggest a smaller number of layers for ucore
Atry 40?
Aor maybe 30
A30 seems good
Ai used 69 so they'd be 70 but ostree-rs-ext adds 2 more and they became 71 
A20 is also not bad
A oh
AGitHub
Adds meta packages for docker compose and docker buildx, which are large executables of around 60mb.
Full Changelog: v0.8.4...v0.8.5
Full Changelog: v0.8.4...v0.8.5
IHi @Kyle Gospo, I don't understand this commit: https://github.com/ublue-os/bluefin/pull/1580. What is "undefined behavior"? Sorry to bother you, but that PR broke my custom build and I want to understand why it happend
RHaving /usr/etc merge into /etc wasn't documented, and wasn't designed to be used as we did. From what I understand, it was an internal functionality of rpm-ostree, meant to be used for non-OCI workflows and/or when layering locally.
It also started causing issues when we were rechunking our OCI images using the hhd-dev/rechunk action
It also started causing issues when we were rechunking our OCI images using the hhd-dev/rechunk action
Xwriting to /usr/etc/ at build time is apparently undocumented and undefined behavior with rpm-ostree, and writing to /etc/ does the same thing, we at bluebuild wrote an announcement of this, but it's still unreleased, there's a couple things to do first: https://github.com/blue-build/website/pull/65/files
Ayes and no. Essentially the code was written assuming only /etc exists, which caused them to merge during deployment. This merge was a byproduct. If you look at the podman PR for bootc, it will try to move /etc to /usr/etc and fail because it exists. Therefore we slowly need to start migrating
Ahowever the keyword here is SLOWLY. I want to have full backward compatibility with original ublue images prior to this. This includes merging /usr/etc to /etc the exact same way rpm-ostree would
Aand if there are any deployment issues with rechunk and /usr/etc existing I promise to fix them. I already fixed most of them.
Aif ublue starts breaking downstream images because of this, imo you should consider reverting the PR and letting rechunk handle it until we can define a behavior for /usr/etc existing
RI didn't mean to point blame towards the rechunk action. I just meant rechunk didn't expect this because it's not the way rpm-ostree expects, and therefore it didn't work immediately. This sparked the conversation about how we should be handling config files in the future.
AOf course no offense. It is a bit of undefined behavior that you came to expect with your images. So lets keep it that way and move slowly instead. In my opinion
Athere is no rush, we can tweak the merging in the action as necessary until everything works as expected
AIn the meantime, lets setup a communication channel with the redhat folk so that bootc can also be prepared to handle the quirks we found
Ahttps://github.com/hhd-dev/rechunk/issues/2 i started this issue to track this
GitHub
Lets use this issue to track quirks inherent to booting an OCI image. Hopefully, when this issue closes it will be possible for someone to boot an image made with FROM fedora:40 First lets begin wi...
AAlso the last version of rechunk will also log all the files it finds under /usr/etc to ease this migration
Abut again theres no rush here
Awe are not anywhere close to migrating to bootc under podman. Until then, both bootc and rpm-ostree will have the same behavior so you can still rely on it
AI was not notified to it by Colins. I came to the realization by reading the ostree source code across all libraries when building rechunk
AAnd in that effort, I had ostree panic and not boot because both dirs existed, then had to merge them, then saw how rpm-ostree and ostree-rs-ext handled it etc.
FI will edit the blog to mention that Collins notified Ublue folks only
Aoh so its official
Awell in that case
Alol
