and if there are any deployment issues with rechunk and /usr/etc existing I promise to fix them. I a
and 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
Awell good thing he did
Anobody notified me lmao
RI've not heard anything from Colin directly. Did I miss something?
FI mean, Kyle mentioned that Colins told him that
A:clueless:
FOr he maybe got informed indirectly from Colins, idk
Alets ask Kyle
Jwhat broke in your build?
IThat 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".
IThanks everyone for clarifing!
Jyeah, had no idea this was even a thing in rpm-ostree
Jwell, with everything finishing and landing in fedora I guess this is the cycle we bring out our dead lol.
IIn 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
AGl PhD is a long journey
ABeen there trying to wrap up
FOCI world is unfortunately unstable by it's nature
FYou learn something new every day
FBut let's hope that there will be less breaking changes in the future
2`
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?
2stdlib.h
2This should be easy to reproduce as I installed every binary from homebrew and cloned kickstart.nvim which contains treesitter
IEcon PhDs are 5 years in the US. And I'm going to a US-style institute.
N@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.
NI 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.
Anice to hear, no rush
J@antheas ~450MB update on cosmic today, new kernel
Adamn bazzite is like 1gb when kernel updates
2Anyone use neovim+treesitter on uBlue?
Bi install neovim and all the extras required for it through brew
2I had my issue resolved see #
other-dev
other-devBNeal Gompa asked me "Can you update the 
https://src.fedoraproject.org/rpms/incus/blob/rawhide/f/incus.spec#_21
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
K@bketelsen Need a little more context
KLook like this was already reviewed, so this is to rebuild for a recent dependency change I assume?
Bhere's the PR - https://src.fedoraproject.org/rpms/incus/pull-request/2 it's a month old change for incus 6.2 in rawhide. I'm guessing I should increment the release to 4?
Byes, it's actually a fix.
