Bug 16238 - abnormal behaviour of kernel management
Summary: abnormal behaviour of kernel management
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-06-28 13:42 CEST by igor ivanov
Modified: 2015-06-28 14:03 CEST (History)
1 user (show)

See Also:
Source RPM: nvidia-current-kernel-desktop-latest-346.72-2.mga5.nonfree nvidia-current-kernel-3.19.8-desktop-3.mga5-346.72-2.mga5.nonfree
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description igor ivanov 2015-06-28 13:42:41 CEST 
Description of problem:after upgrading mga4 to mga5, I have removed old kernels:
# urpme kernel-*-3.14.43-1.mga4-1-1.mga4.x86_64.rpm
where *= desktop,server
after that, the packages

nvidia-current-kernel-desktop-latest-346.72-2.mga5.nonfree
nvidia-current-kernel-3.19.8-desktop-3.mga5-346.72-2.mga5.nonfree

were declared as orphans, BUT NOT THE SERVER EQUIVALENT PACKAGES:

nvidia-current-kernel-server-latest-346.72-2.mga5.nonfree
nvidia-current-kernel-3.19.8-server-3.mga5-346.72-2.mga5.nonfree

why this dissymetry? 
is it possible to safely remove them with the command
# urpme --auto-orphans
 
Version-Release number of selected component (if applicable):


How reproducible:
upgrade mageia4 64 to mageia 5 and remove the old kernels


Steps to Reproduce:
1.upgrade mageia4 64 to mageia5 64
2.[root@mageia5_64 toto]# urpme kernel-[desktop,server]3.14.43-1.mga4-1-1.mga4.x86_64.rpm
3.see the result


Reproducible: 

Steps to Reproduce:
Comment 1 Sander Lepik 2015-06-28 13:46:29 CEST 
If it suggests to remove nvidia-current-kernel-desktop-latest then it makes me think that you are running on kernel-server kernel?

What's the output of "uname -r"?

Keywords: (none) => NEEDINFO
CC: (none) => mageia

Comment 2 igor ivanov 2015-06-28 13:55:20 CEST 
(In reply to Sander Lepik from comment #1)
> If it suggests to remove nvidia-current-kernel-desktop-latest then it makes
> me think that you are running on kernel-server kernel?
> 
> What's the output of "uname -r"?

it's true but the problem is: I have rebooted under desktop kernel:

[toto@mageia5_64 ~]$ uname -a
Linux mageia5_64 3.19.8-desktop-3.mga5 #1 SMP Sat Jun 13 17:05:48 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

I have reinstall the kernels

nvidia-current-kernel-desktop-latest-346.72-2.mga5.nonfree
nvidia-current-kernel-3.19.8-desktop-3.mga5-346.72-2.mga5.nonfree

using urpmi, and after that:

[root@mageia5_64 alain4]# urpme --test --auto-orphans
Aucun orphelin à supprimer  (no orphan has to be removed)

strange, isn't it?
Comment 3 igor ivanov 2015-06-28 14:00:25 CEST 
sorry, it's normal, I am under desktop kernel
today it's very hot in France, it prevents me to safely think

let's consider the bug as closed
Comment 4 Sander Lepik 2015-06-28 14:03:38 CEST 
It's normal behavior indeed. It won't remove kernel-server as this one you probably installed manually. The desktop one was pulled in by some other package. So if you switched to kernel-server and ran urpme --auto-orphans, then it removed the automatically installed packages as it thought they are no more needed. If you reinstall nvidia-current-kernel-desktop-latest manually then it shouldn't propose to remove it.

I'll close it as invalid, reopen if needed.

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.