Bug 189944 - yum doesn't install SDL_image-1.2.4-5.fc5.i386 on x86_64
Summary: yum doesn't install SDL_image-1.2.4-5.fc5.i386 on x86_64
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: SDL_image
Version: 5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-25 23:58 UTC by Phil Wirtz
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-01-31 14:52:19 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Phil Wirtz 2006-04-25 23:58:58 UTC 
Description of problem:


Version-Release number of selected component (if
applicable):SDL_image-1.2.4-5.fc5.i386


How reproducible:consistent


Steps to Reproduce:
1.yum upgrade SDL_image
2.
3.
  
Actual results:Parsing package install arguments
No Match for argument: SDL-image
Nothing to do



Expected results: pkg with dep installed


Additional info:bug report #189939 (pkg uqm)
problem seems to problem with yum extras repository wiil file report on
component yum . core pkg SDL-1.2.9-5.2.1.i386.rpm installed ok
Comment 1 Brian Pepple 2006-04-26 00:10:38 UTC 
Are you doing 'yum instal SDL_image'?  Your error message says that your trying
to install 'SDL-image', which doesn't exist.
Comment 2 Brian Pepple 2006-04-26 00:11:41 UTC 
Whoops, that shoud be be 'yum install SDL_image' in comment #1.
Comment 3 Brian Pepple 2006-04-27 16:51:48 UTC 
Did you try the suggestion from comment #1?
Comment 4 Phil Wirtz 2006-04-27 21:57:32 UTC 
rpm -e SDL_image-1.2.4-5.fc5.i386
 yum install SDL_image
after 5 faile tries to get primary.xml.gz
Added 808 new packages, deleted 156 old in 6.98 seconds
Parsing package install arguments
Nothing to do
Comment 5 Brian Pepple 2007-01-09 18:09:54 UTC 
Phil, is this bug still present in FC5 or FC6?
Comment 6 Brian Pepple 2007-01-31 14:52:19 UTC 
Closing since no reponse from reporter.  If this bug is still present, please
re-open.
Note You need to log in before you can comment on or make changes to this bug.