Bug 30504 - Are kernel numbers still matching
Summary: Are kernel numbers still matching
Status: RESOLVED DUPLICATE of bug 29830
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-03 18:29 CEST by Norbert Kieffer
Modified: 2022-06-03 18:57 CEST (History)
0 users

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments

Description Norbert Kieffer 2022-06-03 18:29:28 CEST
Description of problem:
After a deep clean up I decided to re install Mageia 8

First stage : installation from an Iso put in a usb key .

Result :
Are installed
- kernel-desktop-5.10.16-1.mga8
-kernel-desktop-latest
- kernel-desktop-devel-5.10.16-1.mga8
-kernel-desktop-devel-latest

OK

Stop and start computer

Then upgrade first part (11 rmp : glibc etc)

Stop and start computer

general upgrade ( some 480 rmp)

Are installed now : 
- kernel-desktop-5.10.16-1.mga8	normal
- kernel-desktop-5.15.43-1.mga8	normal  the last one upgrated (used for boot)
-kernel-desktop-latest
- kernel-desktop-devel-5.10.16-1.mga8 	normal
- kernel-desktop-devel-5.17.11-1.mga8 	????	(used for boot)
-kernel-desktop-devel-latest

NOTICE :
-kernel-desktop-5.17.11-1.mga8    does not exist !
- kernel-desktop-devel-5.-15-43.mga8 exist !




Version-Release number of selected component (if applicable):


How reproducible:
Probably do a new installation but I do not want to try

I deleted - kernel-desktop-devel-5.17.11-1.mga8 and activated kernel-desktop-devel-5.-15-43.mga8 . Hope it is correct .
 Is it finished that the numbers of the kernel and the kernel-devel are the same ?
  



Steps to Reproduce:
1.
2.
3.
Comment 1 sturmvogel 2022-06-03 18:57:07 CEST
5.17.11 is in backports. You are hit by bug 29830
Comment 2 sturmvogel 2022-06-03 18:57:44 CEST
Dup of bug 29830

*** This bug has been marked as a duplicate of bug 29830 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


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