PDA

View Full Version : FC22 broken dependencies akmods kernel-devel



pitonyak
11th November 2015, 12:24 AM
There are broken dependencies in FC22. Any way to find out what that broken dependency is?

DNF lists


akmods 0.5.4-1.fc22
kernel-debug-devel 4.2.5-201.fc22
kernel-devel 4.2.5-201.fc22

I have no problems in kernel 4.2.3, it is only 4.2.5.

I have this on more than one computer.

When I saw akmods, my first thought that the problem was with the nVidia drivers, but, kernel-devel and kernel-debug-devel leaves me thinking that the problem is with these two kernel packages. Is it just me?

pitonyak
20th November 2015, 12:41 AM
The problem continues with kernel-debug-devel and kernel-devel 4.2.6-200.fc22.

Any thoughts on steps to figure out where the broken dependency lies and what is broken.

What happens if I use "--best --allowerasing" ?

On a whim, I tried this:


dnf repoquery --requires kernel-debug-devel
Last metadata expiration check performed 0:08:38 ago on Thu Nov 19 18:23:45 2015.
perl

So, if I understand that correctly, kernel-debug-devel depends on perl. OK, so why is that a failed dependency?

DBelton
20th November 2015, 05:52 AM
It would help if you would post the output of dnf that shows the actual messages so people can tell what type of dependency problem you are having.

pitonyak
20th November 2015, 06:28 AM
It would help if you would post the output of dnf that shows the actual messages so people can tell what type of dependency problem you are having.

I was hoping for a command that would show that precisely. I summarized it in the first post, but, this is the entire output:


[root@andrew ~]# dnf update
Last metadata expiration check performed 2:42:17 ago on Thu Nov 19 21:24:18 2015.
Dependencies resolved.
================================================== ================================================== ================================================== ====================
Package Arch Version Repository Size
================================================== ================================================== ================================================== ====================
Skipping packages with broken dependencies:
akmods noarch 0.5.4-1.fc22 rpmfusion-free-updates 25 k
kernel-debug-devel x86_64 4.2.6-200.fc22 updates 9.8 M
kernel-devel x86_64 4.2.6-200.fc22 updates 9.7 M

Transaction Summary
================================================== ================================================== ================================================== ====================

Nothing to do.
Complete!

In other words, nothing useful. My reading of this is that it cannot update akmods, kernel-debug-devel, or kernel-devel because they have broken dependencies. I mean I think that all three have a broken dependency on something. I did try to use verbose, but that was still pretty much useless.

I tried "dnf repoquery --requires" to see what the dependency is, but, that only shows perl as a dependency for the kernel stuff.

The latest kernel-devel I have on my system is 4.2.3-200



[root@andrew ~]# rpm -qa | grep -i kernel-devel
kernel-devel-3.19.5-200.fc21.x86_64
kernel-devel-3.19.7-200.fc21.x86_64
kernel-devel-4.2.3-200.fc22.x86_64
kernel-devel-4.1.6-200.fc22.x86_64
kernel-devel-4.0.4-201.fc21.x86_64
kernel-devel-4.1.5-200.fc22.x86_64

I also tried this to understand the problem

[
root@andrew ~]# dnf repoquery --unsatisfiedl
Last metadata expiration check performed 2:56:30 ago on Thu Nov 19 21:24:18 2015.
package kmod-nvidia-4.2.3-200.fc22.x86_64-1:355.11-4.fc22.x86_64 requires kernel-uname-r = 4.2.3-200.fc22.x86_64, but none of the providers can be installed


Way behind on my sleep today, perhaps I will think more clearly in the morning. The above seems to imply the problem is in kmod-nvidia

DBelton
20th November 2015, 04:44 PM
Blah.. dnf and the funky way it handles broken dependencies :(

Try looking in /var/log/dnf.log for better messages, or try using the --best option so it will tell you more about the broken dependencies.

You should be able to run


dnf --best update


But not allow it to go ahead with the update and see the errors it produces.

pitonyak
20th November 2015, 05:25 PM
Oh, that is good to know. The error is rather unexpected


[root@andrew ~]# dnf update --best
Last metadata expiration check performed 1:48:11 ago on Fri Nov 20 09:27:43 2015.
Error: cannot install both kernel-debug-devel-4.2.6-200.fc22.x86_64 and kernel-debug-devel-4.0.4-201.fc21.x86_64.
package akmods-0.5.4-1.fc22.noarch conflicts with kernel-debug-devel provided by kernel-debug-devel-4.1.5-200.fc22.x86_64.
cannot install both kernel-devel-4.2.6-200.fc22.x86_64 and kernel-devel-4.0.4-201.fc21.x86_64.
cannot install both kernel-debug-devel-4.2.6-200.fc22.x86_64 and kernel-debug-devel-4.0.4-201.fc21.x86_64.
cannot install both kernel-debug-devel-4.2.6-200.fc22.x86_64 and kernel-debug-devel-3.19.5-200.fc21.x86_64.
cannot install both kernel-devel-4.2.6-200.fc22.x86_64 and kernel-devel-4.0.4-201.fc21.x86_64.
cannot install both kernel-devel-4.2.6-200.fc22.x86_64 and kernel-devel-3.19.5-200.fc21.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages)

I am currently using 4.2.3, so I do not really care about the older items. So, my gut reaction was to simply allow the older items to be erased:


[root@andrew ~]# dnf update --best --allowerasing
Last metadata expiration check performed 1:52:09 ago on Fri Nov 20 09:27:43 2015.
Error: package akmods-0.5.4-1.fc22.noarch conflicts with kernel-debug-devel provided by kernel-debug-devel-4.2.6-200.fc22.x86_64

I had not expected that particular conflict. I am using the akmod nvidia driver since I had occasional crashes with the nouveau nVidia driver. My best guess is that it was some interaction between VMWare and the video driver, but that is kind of a guess. Stability increased with the akmod driver. That said, i could certainly switch the video driver and then see what happens.

Off hand, does that seem reasonable?

DBelton
20th November 2015, 05:33 PM
You still have some F21 kernel packages installed, and those will be safe to remove.

Actually, you really don't need any of the kernel-debug-devel packages installed. For the kernel-devel and kernel-debug-devel, I would allow it to erase the old packages.

As for the akmods package, that would be taken care of (it appears) if you get rid of your kernel-debug-devel packages that you really don't need to have installed.

Edit:

Firs thing you can do is



dnf remove kernel-debug-devel*


To get rid of those kernel-debug-devel packages

Make sure you keep the kernel-devel package installed You need it for akmods.

pitonyak
20th November 2015, 05:48 PM
I believe that I installed the debug devel kernel stuff so that I can use vmware...

DBelton
20th November 2015, 05:59 PM
I believe that vmware only requires kernel-devel and kernel-headers to be installed. I don't believe it needs the kernel-debug-devel packages.

nzpling
20th November 2015, 09:25 PM
Possibly not much help, but I had the same issue with kernel-devel.
Resolved it by
dnf erase (and dependancies)
dnf autoremove
dnf install (kernel-devel + the removed dependancies)

In my case the dependancies were few - Oracle VirtualBox & it's dependancies, so it wasn't a major issue.

pitonyak
21st November 2015, 09:54 PM
I switched back to the nouveau driver, before there was the statement about not needing the kernel-debug-devel, but, I will follow-up on that. Ironically, when I ran VMWare after a working update, a performance issue that I had in a package running inside a Windows 7 VM, was solved. The software itself worked, but, it was unusable to select text in a library package called Logos. Interesting.

I really appreciate all of the help. I learned much based on all your help. And yes nzpling, your post is also helpful and greatly appreciated.