Bug 429628 - wxGTK version conflicts w wxGTK from dag repo
Summary: wxGTK version conflicts w wxGTK from dag repo
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: wxGTK
Version: el4
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-22 00:25 UTC by Dave Botsch
Modified: 2008-01-22 06:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-22 06:24:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Botsch 2008-01-22 00:25:08 UTC
Description of problem:
Dag's EL4 repo has at least one package (vlc) built against wxGTK2.6 -- epel's
repo has a newer wxGTK - 2.8 - presumably required by packages in epel. Clearly,
this causes issues.


Version-Release number of selected component (if applicable):
2.8.4-4.el4.1


How reproducible:
100%


Steps to Reproduce:
1.install wxGTK from epel (or set up both the epel and dag repos in yum)
2.try doing a 'yum install vlc'
3.failure
  
Actual results:
cannot install vlc due to epel's wxGTK being selected over the dag one

Expected results:
vlc installs

Additional info:
It would be great if you guys could coordinate w. dag (and the other repos out
there) to help avoid issues like this. While I am aware of yum plugins that
allow one to specify repo priorities (in my case, epel is a higher prioritiy
than dag due to my needing the lower versioned epel wine over the higher
versioned dag wine), clearly now I need the lower versioned dag wxGTK over the
higher versioned epel wxGTK - so, I need the priorities in both directions *sigh*

Comment 1 Dan Horák 2008-01-22 06:24:49 UTC
Sorry, but when mixing repos, you must solve the conflicts yourself. Probably an
exclude list containing wxGTK in the EPEL repo definition will workaround this
conflict.


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