Bug 12032 - drakrpm-update tries to install 32bit updates in 64bit system
Summary: drakrpm-update tries to install 32bit updates in 64bit system
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-18 08:17 CET by Pavel Kreuzt
Modified: 2015-03-31 16:05 CEST (History)
1 user (show)

See Also:
Source RPM: rpmdrake-5.49-1.mga3.src.rpm, meta-task-1:3-43.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Pavel Kreuzt 2013-12-18 08:17:38 CET
Description of problem: With the latest kernel updates (from 3.8.13 to 3.10.24) in a 64bit system, drakrpm-update proposes to install newer kernel in 32bit version, and associated module packages too. This happens after installing meta-task update.

Also, a little question: is there any way to automatically remove older unused kernels after upgrade? Other distros have a tool to remove them: you configure it to keep only 3 kernels (for example) and when a kernel update is installed it removes older one to keep only 3 installed kernels.


How reproducible: In 3.8.13 to 3.10.24 update, after meta-task-1:3-43 update


Steps to Reproduce:
1. Trigger update process, and install proposed meta-task update
2. Renew update list, it will propose kernel 3.10.24 update in 32 version

Reproducible: 

Steps to Reproduce:
Comment 1 Thomas Backlund 2013-12-18 08:46:05 CET
Probably a transient issue where x86_64 kernels was not fully synced on the mirrors yet.

CC: (none) => tmb

Comment 2 Pavel Kreuzt 2013-12-18 12:27:31 CET
They were synced, I solved it selecting 64bit packages to update in drakrpm, were they were present already.
Comment 3 Marja Van Waes 2015-03-31 16:05:19 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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


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