Bug 700 - Update of package ruby-atk blocked by ruby-gdkpixbuf2
Summary: Update of package ruby-atk blocked by ruby-gdkpixbuf2
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Rémy CLOUARD (shikamaru)
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-08 04:50 CEST by Dave Hodgins
Modified: 2011-05-08 15:09 CEST (History)
0 users

See Also:
Source RPM: ruby-pango-0.90.8-1.mga1.src.rpm
CVE:
Status comment:


Attachments

Description Dave Hodgins 2011-04-08 04:50:25 CEST
From urpmi --auto-select ...

ruby-atk-0.90.8-1.mga1.i586 (due to conflicts with ruby-glib2-0.90.8-1.mga1.i586, trying to promote ruby-glib2)
ruby-glib2-0.90.8-1.mga1.i586 (in order to keep ruby-gdkpixbuf2-0.19.2-2mdv2010.1.i586)
ruby-pango-0.90.8-1.mga1.i586 (due to conflicts with ruby-glib2-0.90.8-1.mga1.i586, trying to promote ruby-glib2)
Ahmad Samir 2011-05-05 19:29:32 CEST

Assignee: bugsquad => shikamaru

Comment 1 Dave Hodgins 2011-05-06 22:22:39 CEST
Changed rpm.  Currently urpmi --auto-select --debug shows

selecting ruby-pango-0.90.8-1.mga1.i586
set_rejected: ruby-pango-0.19.2-2mdv2010.1.i586
requiring rubygem(glib2)[>= 0.90.8] for ruby-pango-0.90.8-1.mga1.i586
chosen ruby-glib2-0.90.8-1.mga1.i586 for rubygem(glib2)[>= 0.90.8]
selecting ruby-glib2-0.90.8-1.mga1.i586
set_rejected: ruby-glib2-0.19.2-2mdv2010.1.i586

Something about the way urpmi translates rubygem to ruby-RubyGems (which
did previously get installed) is failing for ruby-pango.

Source RPM: ruby-atk-0.90.8-1.mga1.src.rpm => ruby-pango-0.90.8-1.mga1.src.rpm

Comment 2 Rémy CLOUARD (shikamaru) 2011-05-08 15:09:04 CEST
Should be fixed with ruby-gdk_pixbuf2-0.90.8-2

The problem is that the name is different (see the underscore in the name)

Thanks for reporting the bug, please reopen it if you encounter other issues with ruby-gnome2 related packages

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


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