Bug 33005 - rpm installations fail when newer kernel version already installed
Summary: rpm installations fail when newer kernel version already installed
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: RPM stack maintainers
QA Contact:
URL:
Whiteboard:
Keywords: FOR_ERRATA9
Depends on:
Blocks:
 
Reported: 2024-03-22 23:48 CET by Tony Blackwell
Modified: 2024-11-26 12:05 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Tony Blackwell 2024-03-22 23:48:53 CET
Description of problem:
Installed new M9, configured mirror (used aarnet.edu.au), updated system immediately before anything else.
Rebooted.
Then tried to install virtualbox 7.0.14 (via MCC)
Appeared to be proceeding OK but failed at the end with popup message:

1 installation failed.
There was a problwem during the installation.
Package kernel-desktop-6-6-18-1.mga9.x86_64 (which is newer than kernel-desktop-6.5.13-6.mag9.x86_64) is already installed.

This bit me a few days ago interstate, building a friend's first linux computer.
Couldn't in time available find a work-around for that box.  Threw together a second one from his components and confirmed that the problem is bypassed if virtualbox is installed first, before doing the global update.

It's not just virtualbox; I encounted same problem trying to install stellarium (he's an astronomer) although after much mucking around got that to install.  Virtualbox determinedly resists installation - I couldn't prevent the rpm installation from trying to install kernel 6.5.13 even with taking the tick out of that box in package selection.

In ignorance of the facts I'm guessing that the dependencies list for affected packages (there might be lots, or is there some common point in scripts?) needs to be updated, or similar??  I just stumbled on this for these 2 rpm's but they are unlikely to be the only ones.



How reproducible:
Now home again a few days later.  Just reproduced behaviour on spare partition on my main computer.


Steps to Reproduce:
as above
Comment 1 Lewis Smith 2024-03-26 21:47:10 CET
Thank you for the report.

Passing to RPM stack people.

Assignee: bugsquad => rpmstack

Comment 2 Tony Blackwell 2024-05-08 09:40:21 CEST
Seen this a couple more times on new installations.  

Work around is to do the initial installation, then remember to install everything else I want.   Only after that, run the big 'Update your System" for the first time.

The bug is still very real, and seems to mean that any rpm tied to a particular (older) kernel version will not install once the underlying system has been updated to a newer kernel.  I'm sure this is not intended for a package like virtualbox...
Comment 3 Morgan Leijström 2024-11-26 12:03:14 CET
In https://forums.mageia.org/en/viewtopic.php?t=15519, user say he can un-select the offending kernel suggestion in drakrpm.

CC: (none) => fri, mageiatools

Comment 4 Morgan Leijström 2024-11-26 12:05:26 CET
Possibly for errata

Keywords: (none) => FOR_ERRATA9


Note You need to log in before you can comment on or make changes to this bug.