I’m not sure how many have noticed, but DNF hasn’t been downloading zchunk metadata in Fedora since the beginning of this month due to a bug in… And, when that happens, almost nobody will notice (but their metadata downloads will be greatly reduced in size again) Back in July, a bug was found in RHEL 8 that caused a crash if zchunk-enabled repos were found.The bug turned out to be in librepo, where was defined in all recent versions.Fedora has packaging guidelines describing how packages should work.
I try to fix with this but not work:[[email protected] mythcat]# dnf system-upgrade download --refresh --releasever=31--setopt=module_platform_id=platform:f31 --skip-broken Before you continue to ensure that your system is fully upgraded by running "dnf--refresh upgrade".
Do you want to continue [y/N]: y...[[email protected] mythcat]# pkcon refresh force -c -1[[email protected] mythcat]# dnf --releasever=30 --allowerasing downgrade fedora[[email protected] mythcat]# dnf clean all --releasever=32[[email protected] mythcat]# dnf clean all --releasever=31[[email protected] mythcat]# dnf clean all --releasever=30The pkcon tool refresh the cached information about available updates and set the maximum acceptable age for cached metadata, in seconds.
The DNF developers quickly settled on an easy fix, wrapping the define in an so it would only be defined if zchunk was enabled in librepo. This fix made it into Fedora and had no noticeable effect until libdnf was rebuilt early this month.
It turns out that the header file with the define is included as is in libdnf. The method we’ve gone with is to define In 2017, I started working on a new book to teach Linux command line in our online summer training.
I’m so excited to meet with all my friends from KDE!
After missing the conference weekends in Almería and Vienna, I’ll be able to get the full Akademy experience again - including delivering a talk!
Just adding one problem as an issue is also a big help, so please spend 5 minutes of your free time, and add any problem you like.
In this tutorial, I will show you how to rollback from a bad distro update of Fedora 31 to the old one Fedora 30.
Let's start with my pettiest gripe: the lack of a trailing 0 on official releases. This would be okay except for if you look at the Makefile for stable releases, there's still a 0 in the SUBLEVEL filed where stable updates come from.
Official kernel releases are usually versioned like 5.1, 5.2. "But Laura, there's macros to take care of that" yes, in the kernel itself.
The numbers mean nothing at this point except they keep getting larger.