Bug 435924 - gnustep-make-2.0.4-8.fc8.i386 conflicts with make-3.81-10.fc8.i386
Summary: gnustep-make-2.0.4-8.fc8.i386 conflicts with make-3.81-10.fc8.i386
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnustep-make
Version: 8
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Axel Thimm
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 436093 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-04 14:16 UTC by Shaopu Lin
Modified: 2008-03-13 07:41 UTC (History)
1 user (show)

Fixed In Version: 2.0.4-9.fc8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-13 07:41:49 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Shaopu Lin 2008-03-04 14:16:27 UTC 
Description of problem:
Installing gnustep-make with --enablerepo=updates-testing failed because the
testing version of gnustep-make conflicts with make-3.81-10.fc8.i386.
Transaction Check Error:
  file /usr/share/info/make.info.gz from install of
gnustep-make-2.0.4-8.fc8.i386 conflicts with file from package make-3.81-10.fc8.i386

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

How reproducible:
Always

Steps to Reproduce:
1.installing to gnustep-make-2.0.4 with make installed and
--enablerepo=updates-testing
2.
3.
  
Actual results:
Installing failed

Expected results:
Installing should work

Additional info:
Comment 1 Axel Thimm 2008-03-04 21:45:28 UTC 
That's funny, I had this fix already in the specfile and somehow it got killed:

* Fri Feb 22 2008 Axel Thimm <Axel.Thimm> - 2.0.4-8
- Rename make.info to avoid clash with GNU make.

I'll fix that with 2.0.4-9, thanks for reporting!
Comment 2 Karsten Hopp 2008-03-05 12:18:40 UTC 
*** Bug 436093 has been marked as a duplicate of this bug. ***
Comment 3 Fedora Update System 2008-03-13 07:41:47 UTC 
gnustep-make-2.0.4-9.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.