Having /usr/etc merge into /etc wasn't documented, and wasn't designed to be used as we did. From w

Having /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

xyny•8/11/24, 12:13 PM

writing 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

RRobert Having /usr/etc merge into /etc wasn't documented, and wasn't designed to be use...

antheas•8/11/24, 12:29 PM

yes 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

antheas•8/11/24, 12:30 PM

however 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

antheas•8/11/24, 12:30 PM

and if there are any deployment issues with rechunk and /usr/etc existing I promise to fix them. I already fixed most of them.

antheas•8/11/24, 12:32 PM

if 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

Aantheas and if there are any deployment issues with rechunk and /usr/etc existing I prom...

RobertOP•8/11/24, 12:33 PM

I 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.

antheas•8/11/24, 12:34 PM

Of 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

antheas•8/11/24, 12:34 PM

there is no rush, we can tweak the merging in the action as necessary until everything works as expected

antheas•8/11/24, 12:35 PM

In the meantime, lets setup a communication channel with the redhat folk so that bootc can also be prepared to handle the quirks we found

antheas•8/11/24, 12:35 PM

https://github.com/hhd-dev/rechunk/issues/2 i started this issue to track this

GitHub

OCI Image boot quirks or "The road to `FROM fedora: 40`" · Issue #2...

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...

antheas•8/11/24, 12:37 PM

Also the last version of rechunk will also log all the files it finds under /usr/etc to ease this migration

antheas•8/11/24, 12:37 PM

but again theres no rush here

antheas•8/11/24, 12:37 PM

we 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

antheas•8/11/24, 12:39 PM

I was not notified to it by Colins. I came to the realization by reading the ostree source code across all libraries when building rechunk

antheas•8/11/24, 12:39 PM

And 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.

Aantheas I was not notified to it by Colins. I came to the realization by reading the ost...

fiftydinar•8/11/24, 12:42 PM

I will edit the blog to mention that Collins notified Ublue folks only

antheas•8/11/24, 12:43 PM

oh so its official

antheas•8/11/24, 12:43 PM

well in that case

antheas•8/11/24, 12:43 PM

lol

antheas•8/11/24, 12:43 PM

well good thing he did

antheas•8/11/24, 12:43 PM

nobody notified me lmao

RobertOP•8/11/24, 12:43 PM

I've not heard anything from Colin directly. Did I miss something?

fiftydinar•8/11/24, 12:43 PM

I mean, Kyle mentioned that Colins told him that

antheas•8/11/24, 12:44 PM

:clueless:

fiftydinar•8/11/24, 12:45 PM

Or he maybe got informed indirectly from Colins, idk

antheas•8/11/24, 12:46 PM

lets ask Kyle

IIon Hi @Kyle Gospo, I don't understand this commit: https://github.com/ublue-os/blue...

j0rge•8/11/24, 1:26 PM

what broke in your build?

Jj0rge what broke in your build?

Ion•8/11/24, 1:35 PM

#!/usr/bin/env bash

# Tell build process to exit if there are any errors.
set -oue pipefail

rm /usr/etc/skel/.config/autostart/bluefin-firstboot.desktop
rm /usr/etc/yafti.yml
rm /usr/etc/profile.d/bluefin-firstboot.sh

#!/usr/bin/env bash

# Tell build process to exit if there are any errors.
set -oue pipefail

rm /usr/etc/skel/.config/autostart/bluefin-firstboot.desktop
rm /usr/etc/yafti.yml
rm /usr/etc/profile.d/bluefin-firstboot.sh

That was one of the scripts that exited with an error so the build action was failing. Apologies for not being more specific. My images wouldn't get built, not that they "broke".

Ion•8/11/24, 1:36 PM

Thanks everyone for clarifing!

j0rge•8/11/24, 1:36 PM

yeah, had no idea this was even a thing in rpm-ostree

j0rge•8/11/24, 1:37 PM

well, with everything finishing and landing in fedora I guess this is the cycle we bring out our dead lol.

Ion•8/11/24, 2:00 PM

In 10 days I'm moving to Italy for my PhD. I hope we enter a period of stability for the next 6months, because I wont have time to troubleshoot xD

antheas•8/11/24, 2:13 PM

Gl PhD is a long journey

antheas•8/11/24, 2:14 PM

Been there trying to wrap up

fiftydinar•8/11/24, 2:26 PM

OCI world is unfortunately unstable by it's nature

fiftydinar•8/11/24, 2:26 PM

You learn something new every day

fiftydinar•8/11/24, 2:27 PM

But let's hope that there will be less breaking changes in the future

MM2 @Gerblesh brew doesn't name things gcc/g++ etc... utter pain. It's named gcc-13

2Kaleb•8/11/24, 3:25 PM

`
nvim-treesitter[vimdoc]: Error during compilation                                                                                                                       
In file included from src/parser.c:1:                                                                                                                                             
src/tree_sitter/parser.h:10:10: fatal error: 'stdlib.h' file not found

`
nvim-treesitter[vimdoc]: Error during compilation                                                                                                                       
In file included from src/parser.c:1:                                                                                                                                             
src/tree_sitter/parser.h:10:10: fatal error: 'stdlib.h' file not found

Issue with neovim treesitter regarding C compiler.
Anyone know a solution?

2Kaleb•8/11/24, 3:26 PM

stdlib.h

2Kaleb•8/11/24, 3:32 PM

This should be easy to reproduce as I installed every binary from homebrew and cloned kickstart.nvim which contains treesitter

Aantheas Gl PhD is a long journey

Ion•8/11/24, 3:51 PM

Econ PhDs are 5 years in the US. And I'm going to a US-style institute.

Noel•8/11/24, 4:15 PM

@antheas I definitely think that there is a desire from Red Hat and Fedora to have a more open conversation with us given the problems we have been solving. This is based on my experience at Flock and conversations I had with Dan Walsh and others.

Noel•8/11/24, 4:16 PM

I know several of the leaders will be at Devconf US, so it's likely conversations won't happen until at least the week after this one.

antheas•8/11/24, 4:21 PM

nice to hear, no rush

j0rge•8/11/24, 4:21 PM

@antheas ~450MB update on cosmic today, new kernel

antheas•8/11/24, 4:21 PM

damn bazzite is like 1gb when kernel updates

2Kaleb•8/11/24, 5:22 PM

Anyone use neovim+treesitter on uBlue?

22Kaleb Anyone use neovim+treesitter on uBlue?

bketelsen•8/11/24, 8:12 PM

i install neovim and all the extras required for it through brew

2Kaleb•8/11/24, 8:18 PM

I had my issue resolved see #

other-dev

bketelsen•8/11/24, 10:58 PM

Neal Gompa asked me "Can you update the Release:Release: in the spec and add a changelog entry for this?" on my incus PR. What should I update it to? Here's the spec file. I have no idea what I'm doing

https://src.fedoraproject.org/rpms/incus/blob/rawhide/f/incus.spec#_21

#!/usr/bin/env bash # Tell build process to exit if there are any errors. set -oue pipefail rm /usr/etc/skel/.config/autostart/bluefin-firstboot.desktop rm /usr/etc/yafti.yml rm /usr/etc/profile.d/bluefin-firstboot.sh

` nvim-treesitter[vimdoc]: Error during compilation In file included from src/parser.c:1: src/tree_sitter/parser.h:10:10: fatal error: 'stdlib.h' file not found

Having /usr/etc merge into /etc wasn't documented, and wasn't designed to be used as we did. From w

Similar Threads

Similar Threads

Similar Threads