Bug 5646 - libpeas-gir1 requires libpeas1.0_0 = 1.4.0-1.mga2
Summary: libpeas-gir1 requires libpeas1.0_0 = 1.4.0-1.mga2
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 3342
  Show dependency tree / graph
 
Reported: 2012-04-27 22:28 CEST by Dave Hodgins
Modified: 2012-04-28 06:20 CEST (History)
3 users (show)

See Also:
Source RPM: libpeas-1.4.0-1.mga2.src.rpm
CVE:
Status comment:

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

Description Dave Hodgins 2012-04-27 22:28:15 CEST 
During upgrade test using pre-release rc dvd I encountered

Installation failed:
        libpeas1.0_0 = 1.4.0-1.mga2 is needed by libpeas-gir1.0-1.4.0-1.mga2.i586

I don't see what's wrong ...

# urpmq --requires libpeas-gir1|grep libpeas
libpeas1.0_0[== 1.4.0-1.mga2]

# urpmq --provides libpeas1.0_0|grep libpeas
libpeas0[== 1.4.0-1.mga2]
libpeas-1.0.so.0
libpeas1.0_0[== 1.4.0-1.mga2]
libpeas1.0_0(x86-32)[== 1.4.0-1.mga2]

# ll libpeas*
-r--r--r-- 1 root root 43745 Mar 28 09:33 libpeas1.0_0-1.4.0-1.mga2.i586.rpm
-r--r--r-- 1 root root 45409 Mar 28 09:33 libpeas-data-1.4.0-1.mga2.i586.rpm
-r--r--r-- 1 root root  7628 Mar 28 09:33 libpeas-gir1.0-1.4.0-1.mga2.i586.rpm
-r--r--r-- 1 root root 21639 Mar 28 09:33 libpeas-gtk1.0_0-1.4.0-1.mga2.i586.rpm
-r--r--r-- 1 root root  6479 Mar 28 09:33 libpeas-gtk-gir1.0-1.4.0-1.mga2.i586.rpm
Manuel Hiebel 2012-04-27 22:47:55 CEST

CC: (none) => fundawang, jani.valimaa, olav
Blocks: (none) => 3342

Comment 1 Funda Wang 2012-04-28 05:40:03 CEST 
Is there any debug.log ?
Comment 2 Dave Hodgins 2012-04-28 06:20:50 CEST 
Sorry, meant to close the page where I was submitting this, as I
figured out this must be a urpmi cascade error, caused by bug 5645,
but must have it the submit by mistake, and then went offline to test
an upgrade using the dual-cd.

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