Bug 16510

Summary: conflicting packages (i586) on x86_64 system
Product: Mageia Reporter: Pierre Fortin <pf>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: 5Keywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: urpmi output

Description Pierre Fortin 2015-07-31 13:54:37 CEST 
Description of problem: Did an update about a week ago.  Today, when checking for updates (via mcc), before anything else, I get:

Conflicting Packages
The following packages have to be removed for others to be upgraded:
libharfbuzz0-0.9.36-1.mga5.i586
 (due to missing libicuuc.so.53)
libicu53-53.1-12.mga5.i586
 (due to unsatisfied icu53-data == 1:53.1-12.mga5)
libpango1.0_0-1.36.8-3.mga5.i586
 (due to missing libharfbuzz.so.0,
  due to unsatisfied libpango1.0_0-modules == 1.36.8)
libpango1.0_0-modules-1.36.8-3.mga5.i586
 (due to missing libharfbuzz.so.0,
  due to missing libpangoft2-1.0.so.0,
  due to missing libpango-1.0.so.0)
libqtcore4-4.8.6-9.mga5.i586
 (due to missing libicui18n.so.53,
  due to missing libicuuc.so.53)
libqtgui4-4.8.6-9.mga5.i586
 (due to missing libQtCore.so.4,
  due to missing libQtSvg.so.4)
libqtnetwork4-4.8.6-9.mga5.i586
 (due to missing libQtCore.so.4)
libqtopengl4-4.8.6-9.mga5.i586
 (due to missing libQtCore.so.4,
  due to missing libQtGui.so.4)
libqtsql4-4.8.6-9.mga5.i586
 (due to missing libQtCore.so.4)
libqtsvg4-4.8.6-9.mga5.i586
 (due to missing libQtCore.so.4,
  due to missing libQtGui.so.4)
libqtxml4-4.8.6-9.mga5.i586
 (due to missing libQtCore.so.4)

"rpm -qa | grep i586" produces no output.  So why am I getting "conflicting packages"?

If I close this dialog, I get a list of packages (none checked). Clicking Select all brings this Conflicting Packages list back up.  I can't apply updates today.

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


How reproducible:  first time.


Steps to Reproduce:
1. mcc
2. update your system
3.


Reproducible: 

Steps to Reproduce:
Comment 1 James Kerr 2015-07-31 16:21:13 CEST 
"rpm -qa | grep i586" produces no output

Try:

rpm -qa --last | grep .i586
Comment 2 Jani Välimaa 2015-08-04 16:52:41 CEST 
What's the output of "urpmi --auto-u --debug"?

CC: (none) => jani.valimaa

Comment 3 Pierre Fortin 2015-08-04 21:23:11 CEST 
Created attachment 6902 [details]
urpmi output

re comment#1:

man rpm:
--last Orders the package listing by install time such that the latest packages are at the top.

OK; I missed that -qa doesn't include {i586,x86_64,arch,...}.  BUT... where does it say/imply that --last _will_ add that?  

re comment#2: attached.
Jani Välimaa 2015-08-23 12:12:05 CEST

CC: jani.valimaa => (none)

Comment 4 Marja Van Waes 2015-11-17 20:34:59 CET 
(In reply to Pierre Fortin from comment #3)
> 
> re comment#1:
> 
> man rpm:
> --last Orders the package listing by install time such that the latest
> packages are at the top.
> 
> OK; I missed that -qa doesn't include {i586,x86_64,arch,...}.  BUT... where
> does it say/imply that --last _will_ add that?  
> 

It neither says nor implies that, but when added to "rpm -qa " it does do it:

[marja@localhost Desktop]$ uname -i
x86_64
[marja@localhost Desktop]$ rpm -qa --last | grep .i586
libquicktime0-1.2.4-11.mga6.tainted.i586      Fri 23 Oct 2015 12:58:18 CEST
libdvdcss2-1.3.0-3.mga5.tainted.i586          Tue 21 Jul 2015 10:08:40 CEST
[marja@localhost Desktop]$

CC: (none) => marja11

Comment 5 Marja Van Waes 2016-11-12 10:49:36 CET 
@ Pierre

Is this issue still valid?

If so, then please attach the output of 

   rpm -qa --last | grep .i586

Keywords: (none) => NEEDINFO

Comment 6 Pierre Fortin 2016-11-12 19:15:45 CET 
Not sure.  Trying to get VBox running to test install of mga6.
Anyone trying to fresh install should see this if it's not yet fixed...

All I do is grab a copy of the 64 bit tree only, and install -- for some reason, what should be a simple 64 bit install has the 32 bit media sources checked and the install fails until I turn them off.

Anyway, if I can get VBox sorted out, will test later.
Comment 7 Marja Van Waes 2016-12-08 10:37:30 CET 
Closing as OLD, because since asking whether the issue is still valid, that wasn't confirmed.

Please reopen if needed.

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