Dnf

While I was performing an upgrade of Fedora 41 to 42 on my laptop, I noticed there was package installed since Fedora 38. This package, zfs-dkms-2.2.0-1.fc38.noarch, needed to be removed as it blocked this Fedora 42 upgrade. TL;DR - The solution is to use --noscripts option with rpm command. If you want to see how the zfs-dkms package removed, follow along. Here’s the info about the package: root@benjo:/etc/yum.repos.d# dnf info zfs-dkms Updating and loading repositories: Repositories loaded. Installed packages Name : zfs-dkms Epoch : 0 Version : 2.2.0 Release : 1.fc38 Architecture : noarch Installed size : 56.9 MiB Source : zfs-dkms-2.2.0-1.fc38.src.rpm From repository : zfs Summary : Kernel module(s) (dkms) URL : https://github.com/openzfs/zfs License : CDDL Description : This package contains the dkms ZFS kernel modules. Vendor : <NULL> Available packages Name : zfs-dkms Epoch : 0 Version : 2.3.2 Release : 1.fc41 Architecture : noarch Download size : 31.0 MiB Installed size : 58.6 MiB Source : zfs-dkms-2.3.2-1.fc41.src.rpm Repository : zfs Summary : Kernel module(s) (dkms) URL : https://github.com/openzfs/zfs License : CDDL Description : This package contains the dkms ZFS kernel modules. Vendor Let’s try to remove it normally: ...

Recently I need to install a package called Lmod on a Red Hat 8 server. Lmod is available from RHEL 8 EPEL8 repository, however it has a dependency called lua-filesystem which is only available from codeready-builder repository. On my RHEL 8 server, the codeready-builder repository is not enabled by default. Here is how I’ve got Lmod installed manually: # subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms # dnf install Lmod Looking at the above commands, I needed to enable the codeready-builder-for-rhel-8-x86_64-rpms first before installing Lmod. The thing is, I’m going to forget that Lmod requires lua-filesystem which is not available from the same repository as Lmod unless I write it down somewhere. Or better yet, let’s automate it with Ansible! ...

On Fedora or CentOS, on way to find out what package providing a file we can use yum whatprovides [FILENAME] or dnf whatprovides [FILENAME] on a DNF-aware system. # dnf whatprovides tmux Last metadata expiration check: 2:33:06 ago on Wed 09 Sep 2020 09:45:07 PM AEST. tmux-3.0a-2.fc32.x86_64 : A terminal multiplexer Repo : @System Matched from: Provide : tmux = 3.0a-2.fc32 tmux-3.0a-2.fc32.x86_64 : A terminal multiplexer Repo : fedora Matched from: Provide : tmux = 3.0a-2.fc32 I really need this similar tool on Gentoo, and it looks like the emerge command doesn’t have this function built it. Fortunately, there is a utility called e-file (provided by pfl package) which kinda provides this whatprovides option as in yum and dnf. ...

While newer version of a package on Linux system is generally a good thing, and we should upgrade it, there is times when we should hold on to the older version. For instance, Fedora 32 just released a newer version of the kernel package 5.8.4 recently, and with this version, the zfs module, version 0.8.4, can’t be built. Therefore, if your Fedora system uses ZFS, like some of my machines, you’ll end up not seeing any ZFS dataset or pools. ...

I’m still running Fedora 31 on my main desktop though Fedora 32 beta has been out for a while. The only reason that stops me from jumping to F32 now is because ZFS 0.8.3 is not compatible with the kernel 5.6.* on F32. Rumor has it, ZFS 0.8.4 will support kernel 5.6. Tonight, while doing the system update with sudo dnf update -y on F31 desktop, I noticed that the kernel for F31 is now kernel-5.6.6-200.fc31.x86_64. Wait, what? I didn’t interrupt the update process, and let it run till finish. ...