librepo-1.9.6 has a major bug that will cause a segfault when a
repository has zchunk metadata. To temporarily work around the
problem, set zchunk=False in /etc/dnf/dnf.conf or wait until the next
updates push comes out
About a week ago, we disabled zchunk metadata in the main F30
repository because of arm-specific compose problems. The problems
were fixed and we enabled zchunk metadata in F30 updates-testing
yesterday, but, in the interval when there were no zchunk-enabled
repositories, librepo-1.9.6 was released, and it has a major bug where
it segfaults whenever dnf update is run on a repository with zchunk
We've disabled zchunk metadata for F30 updates-testing and doing a new
I have submitted a fix for the bug, but for now any F30 users need
to do one of the following:
* Wait until the next updates push is out. It won't have zchunk
metadata, so updates will work normally again.
* Set zchunk=False in /etc/dnf/dnf.conf. This will force dnf to fall
back to non-zchunk metadata, bypassing the bug.
Many apologies for the inconvenience.