Bug 162665 - bazaar and gd-progs have conflicting programs -- /usr/bin/annotate
bazaar and gd-progs have conflicting programs -- /usr/bin/annotate
Product: Fedora
Classification: Fedora
Component: bazaar (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Shahms E. King
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2005-07-07 09:15 EDT by Toshio Kuratomi
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: 1.4.2-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-07 15:55:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Toshio Kuratomi 2005-07-07 09:15:14 EDT
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.


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

How reproducible:

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

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 10:57:44 EDT
Thanks for the report, I will rename annotate to baz-annotate in the bazaar package.
Comment 2 Shahms E. King 2005-07-07 15:55:17 EDT
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.