Tootfinder

PSA/TIL #fedora dracut does an fsfreeze on /boot - so do not do something like:
cd /boot
dracut --debug ... > dracut.debug 2>&1
because then the system starts locking up on any access to /boot with unkillable processes.
Discovered the hard way.

""[…] it is our pleasure to announce the availability of #Fedora #Linux 43 beta! This release comes packed with the latest version upgrades of existing features, plus a few new ones too. As with every beta release, this is your opportunity to test out the upcoming Fedora Linux release a…

I've just fought #fedora 42's into submission on my desktop. I added a 'omit_dracutmodules' to a /etc/dracut.conf.d/99davefix-2025.conf with a whole bunch of unused things and it's booting happily now.
It looks like the problem is that, somewhere about a month ago, as a 42 update, Dracut got bumped, and a lot more devices were added as default in the 'host_only (n…

""[…] one message came through clearly: as we move forward, we should take the opportunity to improve the [#Fedora packager workflow] model rather than simply replicate it. The conversation focused on three key areas: package ownership, artifact storage, and Packit integration.
[…]
Key takeaways include:
* A Shift to Merge Requests: There is strong momentum to make …

J'ai étudié et testé CoreOS et je suis tombé dans un rabbit hole 🙈 mais j'ai enfin publié mes 12 notes !
#Fedora

PSA for users of #Fedora Linux 41 and 42:
The jump from #Linux 6.16.y to 6.17.y will soon happen in updates-testing; a few days later the new #kernel series will become a regular update.

Another post on #Quansight PBC blog: "BLAS/LAPACK #packaging"
#BLAS and #LAPACK are the standard libraries for linear algebra. The original implementation, often called Netlib LAPACK, developed since the 1980s, nowadays serves primarily as the origin of the standard interface, the reference implementation and a conformance test suite. The end users usually use optimized implementations of the same interfaces. The choice ranges from generically tuned libraries such as OpenBLAS and BLIS, through libraries focused on specific hardware such as Intel® oneMKL, Arm Performance Libraries or the Accelerate framework on macOS, to ATLAS that aims to automatically optimize for a specific system.
The diversity of available libraries, developed in parallel with the standard interfaces, along with vendor-specific extensions and further downstream changes, adds quite a bit of complexity around using these libraries in software, and distributing such software afterwards. This problem entangles implementation authors, consumer software authors, build system maintainers and distribution maintainers. Software authors generally wish to distribute their packages built against a generically optimized BLAS/LAPACK implementation. Advanced users often wish to be able to use a different implementation, more suited to their particular needs. Distributions wish to be able to consistently build software against their system libraries, and ideally provide users the ability to switch between different implementations. Then, build systems need to provide the scaffolding for all of that.
I have recently taken up the work to provide such a scaffolding for the Meson build system; to add support for BLAS and LAPACK dependencies to Meson. While working on it, I had to learn a lot about BLAS/LAPACK packaging: not only how the different implementations differ from one another, but also what is changed by their respective downstream packaging. In this blog post, I would like to organize and share what I have learned.
"""
#CondaForge #Debian #Fedora #Gentoo

Right, that's my desktop upto #fedora 43 beta.

PSA for users that regularly test #Fedora Beta as well as proposed updates once the new version was released:
Do not enable updates-testing[1] by modifying /etc/yum.repos.d/fedora-updates-testing.repo; instead do it like this:
$ sudo dnf config-manager setopt updates-testing.enabled=true
Otherwise updates-testing will be disabled shortly before the release of a new version (t…

I’ve been using #Secureblue

Either someone found the vanilla #linux-next builds fpr #s390x useful, which I enabled a few days ago in my #Fedora Linux

Hmm my #Fedora 42 is unhappy with yesterdays 6.15.9-201 - falling back to 8-200 is fine.
Got as far as 'basic target' but no further; it's not hung (caps lock and ctrl-alt-del work). Time to break out some systemd options to get some more debug. Nothing hit the logs on disk.

Wondering when's the best time to prevent #LinuxKernel regressions from hitting #Fedora #Linux?
It's now, as the first pre-release of

Once again, a #CMake project is breaking compatibility with systems that aren't building its dependencies via CMake (but are using Meson instead). Because why use pkg-config when you can use generated CMake configs instead?
#VcPkg. Surely accidental, but why not bash #Microsoft for breaking Linux packages anyway?
#Fedora #Gentoo #packaging

PSA: #KiCad is not working on #Fedora 43 at the moment due to some Python oddity. Hang back for the moment.
https://

Anyone here that cares about all of the following or knows someone who does:
* #s390
* #Fedora
* #LinuxKernel
I'm wondering if its worth enabling s390 for some or all …

Added a graphic showing the dependency tree of the #Linux @kernel-vanilla #Fedora coprs to https://fedoraproject.org/wi…

The release of #Linux 6.17[1] brought a few hours of calmness to the #kernel vanilla repos for #Fedora[2], as that means they just ship three different versions[3]. 😊
Soon the craziness will…