dnf wants to update a package that isn't even installed.. What to do?

asked 2018-10-01 13:25:47 -0500

440 ●11 ●22 ●33

updated 2018-10-01 14:16:29 -0500

Hi, I am encountering a weird situation where dnf tries to update kernel-debug-modules but complains that it is not installed. The latter one is right, it's not installed, and it doesn't need updating, but why does dnf think it should find an update for that package?

sudo dnf update --refresh --enablerepo=updates-testing kernel* (the command I use to install kernels from testing repo) says:

Last metadata expiration check: 0:00:00 ago ...
Package kernel-debug-modules not installed, cannot update it.
No match for argument: kernel-debug-modules-4.18.10-200.fc28.x86_64.rpm
Error: No packages marked for upgrade.

rpm -qa kernel-debug-modules does not return anything. dnf list installed | grep debug does not return anything.

I thought rebuilding the RPM database may help. So after backing it up, I ran

sudo rpm --rebuilddb

but that didn't help either

How can I fix this?

answered 2018-10-01 18:28:32 -0500

villykruse
4657 ●3 ●248 ●90

You need to qoute the wildcard of the dnf command. I beleive your current directory has a file called kernel-debug-modules-4.18.10-200.fc28.x86_64.rpm and the shell would then expand kernel* by the name of that file.

You should do:

sudo dnf update --refresh --enablerepo=updates-testing 'kernel*'

Notice the qoutes around kernel*.

edit flag offensive delete link

Comments

Thanks @villykruse, that helped. However, I am surprised because previously, for a long time, I never had to quote the kernel* term. When you say "your current directory has a file called ...", what directory?

Another issue related to that is that when I run the above command now, dnf wants to reinstall kernel 4.18.10-200. That surprised me because 1.) have installed 4.18.10 from stable already and it works fine, 2.) according to packages that 4.18.10 isn't even in testing anymore. But maybe that's a whole other issue. I am confused.

gobigobi66 ( 2018-10-02 09:17:57 -0500 )edit

For a long time you never had a file with a name starting with "kernel" in the current directory. The current directory is the one you have "cd"d to.

I also seen once that "dnf update" will reinstall the current kernel. You could call it a bug or just a quirk.

villykruse ( 2018-10-02 10:53:33 -0500 )edit

Oh sure. How stupid. Fixed it. (Had a .rpm left there that I downloaded from the build system). Thanks for your help.

gobigobi66 ( 2018-10-02 15:16:39 -0500 )edit

add a comment

dnf wants to update a package that isn't even installed.. What to do?

1 Answer

Comments

Question Tools

Stats

Related questions

dnf wants to update a package that isn't even installed.. What to do? edit

1 Answer

Comments

Question Tools

Stats

Related questions

dnf wants to update a package that isn't even installed.. What to do?