@knurd42@social.linux.pizza2025-10-15 12:44:36
@knurd42@social.linux.pizza2025-10-15 12:44:36
@cdamian@rls.social2025-10-28 15:05:51
@knurd42@social.linux.pizza2025-10-12 09:45:59
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…
@midtsveen@social.linux.pizza2025-11-01 18:15:52
@knurd42@social.linux.pizza2025-10-13 10:19:00
Wondering when's the best time to prevent #LinuxKernel regressions from hitting #Fedora #Linux?
It's now, as the first pre-release of
@selea@social.linux.pizza2025-10-31 09:56:47
@penguin42@mastodon.org.uk2025-10-03 23:29:06
@knurd42@social.linux.pizza2025-09-16 15:17:15
@midtsveen@social.linux.pizza2025-09-07 17:08:13
I’ve been using #Secureblue
@stephane_klein@social.coop2025-10-19 17:49:16
J'ai étudié et testé CoreOS et je suis tombé dans un rabbit hole 🙈 mais j'ai enfin publié mes 12 notes !
#Fedora
@knurd42@social.linux.pizza2025-10-08 10:21:31
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 …
@penguin42@mastodon.org.uk2025-08-23 14:28:33
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.
@mgorny@pol.social2025-10-27 19:11:05
@penguin42@mastodon.org.uk2025-08-23 20:40:54
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…
@knurd42@social.linux.pizza2025-10-21 10:48:36
""[…] 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 …
@penguin42@mastodon.org.uk2025-09-17 15:27:37
Right, that's my desktop upto #fedora 43 beta.
@mgorny@social.treehouse.systems2025-11-02 19:46:20
According to #FreePG right now: #ArchLinux, #Debian, #Fedora, #NixOS and #Ubuntu. Now #Gentoo joins that list, except that instead of silently making intrusive patching on top of GnuPG, we provide it as a separate package (app-crypt/freepg), and mark appropriately:
$ gpg --version
gpg (GnuPG) 2.5.13-freepg
@knurd42@social.linux.pizza2025-10-20 10:26:22
@knurd42@social.linux.pizza2025-09-29 08:50:02
@mgorny@social.treehouse.systems2025-10-27 19:09:43
There should be a policy that when a package provides multiple build systems for itself, and you're building it with #CMake, you should always remove all installed CMake files to make software developed on your platform portable.
#Debian #Fedora #Gentoo #packaging
@mgorny@social.treehouse.systems2025-08-18 04:11:41
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
@mgorny@social.treehouse.systems2025-10-23 16:55:56
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