libdnf
dnf
Additional notes: The builds contain new modular fail-safe mechanism, but modify it to not fail on installing modular RPM packages without modular metadata, but only print a warning.
Please login to add feedback.
0 | 0 | Test Case base update cli |
0 | 0 | Test Case langpacks packages |
This update has been submitted for testing by pkratoch.
This update test gating status has been changed to 'waiting'.
This update test gating status has been changed to 'ignored'.
openQA testing indicates that this is causing crashes in PackageKit. This happens in the test which tests enrolling to a FreeIPA domain using Cockpit (which does some package installs via PK, IIRC) and in the GNOME desktop update test, when refreshing available updates. Tarballs of /var/log and the crash dump directories can be found in affected tests, like this one - coredump.tar.gz is the coredumpctl-captured dump, spoolabrt.tar.gz is the ABRT-captured crash directory, and var_log.tar.gz has the entire contents of /var/log .
This update has been pushed to testing.
https://www.happyassassin.net/temp/dnf_FEDORA-2019-58c2d3f1aa_bt.txt is the best backtrace I can get.
I concur - packagekit is core dumping.
I saw a segmentation fault in PackageKit in libdnf::Repo::Impl::detachLibsolvRepo at /usr/src/debug/libdnf-0.35.1-1.fc30.x86_64/libdnf/repo/Repo.cpp:1347 I reported the crash in #1727343 Should that report be reassigned to libdnf?
The backtrace I posted was completely wrong, sorry, because I had a different libdnf on the system where I got it. The correct backtrace should be the one at https://bugzilla.redhat.com/show_bug.cgi?id=1727424 .
Adding -1 to close the release.
This update has been obsoleted.