Bug 17297

Summary:	Latest update to kernel tries to update to incorrect architecture.
Product:	Mageia	Reporter:	Luke Jones <luke.nukem.jones>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	nic, tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Luke Jones 2015-12-05 22:11:01 CET

Description of problem:

Latest update in cauldron tries to update the kernel to the incorrect architecture. I have no i586 kernels installed.


Summary of packages to be installed is:
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "Nonfree Release")
  nvidia-current-doc-html        352.63       2.mga6.nonfr> x86_64  
  nvidia-current-kernel-4.3.0-d> 352.63       5.mga6.nonfr> x86_64  
  nvidia-current-kernel-desktop> 352.63       5.mga6.nonfr> x86_64  
  x11-driver-video-nvidia-curre> 352.63       2.mga6.nonfr> x86_64  
(medium "Core 32bit Release")
  kernel-desktop-4.3.0-5.mga6    1            1.mga6        i586    
  libopenssl-devel               1.0.2e       1.mga6        i586    
  libopenssl-engines1.0.0        1.0.2e       1.mga6        i586    
  libopenssl1.0.0                1.0.2e       1.mga6        i586 

Final error message is:
Installation failed:	arch(x86_64) conflicts with kernel-desktop-4.3.0-5.mga6-1-1.mga6.i586


How reproducible:

Possibly every time. Need confirmation. 


Steps to Reproduce:
Perform update on an x86_64 computer.


Reproducible: 

Steps to Reproduce:

Comment 1 Thomas Backlund 2015-12-05 23:04:22 CET

you are missing "Core Release" media for some reason.

The Conflicts: arch(x86_64) in 32bit kernels are in place to protect your system from getting wrong kernel arch to install wich it did here.

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => INVALID
Source RPM: kernel-desktop-4.3.0-5.mga6-1-1.mga6.i586 => (none)

Comment 2 Luke Jones 2015-12-06 01:59:58 CET

Thomas I have core release and core update media set up and enabled. Can you provide any other hints as to what is going on?

Status: RESOLVED => UNCONFIRMED
Resolution: INVALID => (none)
Ever confirmed: 1 => 0

Comment 3 Rémi Verschelde 2015-12-06 04:03:49 CET

Somehow you Core Release is maybe lagging behind the Core 32bit Release?

Comment 4 Rémi Verschelde 2015-12-06 04:03:59 CET

s/you/your/

Comment 5 Thomas Backlund 2015-12-06 09:41:45 CET

verify with: urpmq --list-media active

which medias urpmi uses

Comment 6 Nic Baxter 2016-03-29 05:40:11 CEST

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: UNCONFIRMED => RESOLVED
CC: (none) => nic
Resolution: (none) => OLD