Bug 162665 - bazaar and gd-progs have conflicting programs -- /usr/bin/annotate
Summary: bazaar and gd-progs have conflicting programs -- /usr/bin/annotate
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: bazaar
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Shahms E. King
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-07 13:15 UTC by Toshio Kuratomi
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: 1.4.2-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-07-07 19:55:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Toshio Kuratomi 2005-07-07 13:15:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
gd-progs and bazaar each have an annotate program stored in /usr/bin/

The files conflict; preventing installation of both packages at the same time.
One or both packages needs to do some renaming to resolve the situation.

bazaar-1.4.2-1.fc4
gd-progs-2.0.33-2


Version-Release number of selected component (if applicable):
bazaar-1.4.2-1.fc4

How reproducible:
Always

Steps to Reproduce:
1. yum install bazaar
2. yum install gd-progs
3.
  

Actual Results:  esolving Dependencies
Error : Transaction Check Error:   file /usr/bin/annotate from install of gd-progs-2.0.33-2 conflicts with file from package bazaar-1.4.2-1.fc4

Expected Results:  Smooth install of both packages.

Additional info:

Comment 1 Shahms E. King 2005-07-07 14:57:44 UTC
Thanks for the report, I will rename annotate to baz-annotate in the bazaar package.

Comment 2 Shahms E. King 2005-07-07 19:55:17 UTC
After poking through the mailing lists, it appears as though the standalone
annotate binary shouldn't be installed at all.  The specfile now removes the
binary if it gets installed.  This should fix the issue.


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