Red Hat Bugzilla – Bug 1254269
New kernel skipped for dependency problems, but DNF is removing older ones anyway
Last modified: 2015-09-07 06:48:30 EDT
Description of problem:
kernel x86_64 4.1.3-200.fc22 @System 0
kernel-core x86_64 4.1.3-200.fc22 @System 42 M
kernel-devel x86_64 4.1.3-200.fc22 @System 36 M
kernel-modules x86_64 4.1.3-200.fc22 @System 17 M
kernel-modules-extra x86_64 4.1.3-200.fc22 @System 2.1 M
Skipping packages with broken dependencies:
kernel-modules-extra x86_64 4.1.5-200.fc22 updates-testing 2.2 M
kernel-core x86_64 4.1.5-200.fc22 updates-testing 19 M
kernel x86_64 4.1.5-200.fc22 updates-testing 68 k
kernel-devel x86_64 4.1.5-200.fc22 updates-testing 9.5 M
kernel-modules x86_64 4.1.5-200.fc22 updates-testing 18 M
Version-Release number of selected component (if applicable):
I assume always, with the a system and repo in the right state.
Steps to Reproduce:
1. have a kernel with dep problems in the repo
2. try to upgrade
Old kernel is removed
Old kernel stays, at least.
Since I have more than one old kernel, at least my system will still boot after.
Adding the -v flag gives no insight into why the kernel package is skipped. That's incredibly unfortunate -- it's the one thing I want to know.
Thanks for the report. post output of `dnf repoquery kernel*` and installonly_limit in /etc/dnf/dnf.conf, please.
Too late, I'm afraid -- whatever was causing this remotely is now not.
Unfortunately, we cannot reproduce it. If anyone is able to reproduce it, feel free to reopen this and provide the missing data.