@uBlue Members FYI: https://github.com/
@uBlue Members FYI: https://github.com/containers/bootc/issues/899 - also strong recommend you start subbing to bootc issues moving forward as colin wants all the feedback.
ARM Investigation
Anyone have an ARM machine who can quickly test something?
...
$ podman run --rm -it --platform linux/arm64 quay.io/fedora/fedora-silverblue:41
$ podman run --rm -it --platform linux/arm64 quay.io/fedora/fedora-silverblue:41
systemd PR
```h
int write_string_file_full(int dir_fd, const char *fn, const char *line, WriteStringFileFlags flags, const struct timespec *ts, const char *label_fn);
static inline int write_string_file(const char *fn, const char line, WriteStringFileFlags flags) {
return write_string_file_full(AT_FDCWD, fn, line, flags, / ts= / NULL, /label_fn=*/ NULL);
}...
Hey @Noel / @bsherman
Hey @Noel / @bsherman
I've sent an integration request to ublue-os-test for Fedora's Konflux instance to investigate some pipelines. Would be great if you could accept when you get a moment 🙂...
So... apparently this is from udev,
So... apparently this is from udev, specifically from this rule we added in Feb https://github.com/ublue-os/config/pull/214/files
I'm sure the udev rule is mostly benign,and I don't know what circumstances led to this situation where i have lots of "echo to sys fs" procs chewing CPU and refusing to return...
What bothers me is I don't HAVE a Linksys AE1200 USB Wifi dongle. so nothing with that USB ID should have been triggering the udev rule... I don't think I have ANY linksys USB device, for that matter....
Draft: feat: Add featured apps configura...
i did put in this PR for KDE discover. we'll see if it ends up being accepted. but if it does, thats one less thing to have to rely on
yafti
for so it can be streamlinedFedora CountMe Metrics
Just found our usage is getting tracked in Fedora's CountMe metrics.
Trying to make sense of the data...
Trying to make sense of the data...
Bootc Initiative Help Thread
@uBlue Members @Bazzite Contributor I just got off a call for the bootc initiative and if we want bootc enabled by default in Fedora 41, we need more folks to try and help with some issues to push things over the finish line. There are a set of tasks regarding bootupd and composefs. bootupd issues need to be tackled first since composefs issues depends on them, followed by the composefs issues. Here is a link to each of the issues that @Timothée Ravier has laid out:
- bootupd: https://gitlab.com/fedora/ostree/sig/-/issues/1#note_2062751164
- composefs: https://gitlab.com/fedora/ostree/sig/-/issues/35#note_2062769940
We have regular meetings each week to discuss the bootc initiative and if there is sufficient interest, we are happy to set the whole meeting aside to have a discussion regarding any of these issues listed. Here is the meeting information:...
Fedora 41 change: composefs enabled by d...
Bootloader future proofing: https://github.com/ublue-os/main/issues/608#issuecomment-2298684136
Idea time @M2 @bsherman @1/4 Life : A
Idea time @M2 @bsherman @Kyle Gospo : A package-cache just like the kernel-cache.
only thing that caught my eye is that it
only thing that caught my eye is that it won't return the 300 version.