Bug 175997 - mozilla-devel multilib conflicts
mozilla-devel multilib conflicts
Status: CLOSED CANTFIX
Product: Fedora
Classification: Fedora
Component: mozilla (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-12-16 21:32 EST by Christopher Aillon
Modified: 2008-02-08 11:17 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-08 11:17:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Christopher Aillon 2005-12-16 21:32:54 EST
Description of problem:
mozilla-devel-1.7.12-2
	file /usr/include/mozilla-1.7.12/mozilla-config.h from install of
mozilla-devel-1.7.12-2 conflicts with file from package mozilla-devel-1.7.12-2
	file /usr/include/mysql3/mysql/my_config.h from install of
mysqlclient10-devel-3.23.58-6 conflicts with file from package
Comment 1 Christopher Aillon 2005-12-16 21:35:01 EST
Err, that should have been:

	file /usr/include/mozilla-1.7.12/js/jsautocfg.h from install of
mozilla-devel-1.7.12-2 conflicts with file from package mozilla-devel-1.7.12-2
	file /usr/include/mozilla-1.7.12/mozilla-config.h from install of
mozilla-devel-1.7.12-2 conflicts with file from package mozilla-devel-1.7.12-2
Comment 2 Matěj Cepl 2008-02-08 11:17:22 EST
Since this bugzilla report was filed, we have seriously upgraded Gecko-related
packages in Rawhide, which may have resolved this issue. Users who have
experienced this problem are encouraged to upgrade their system to the latest
version of their distribution available.

Closing this bug as CANTFIX. Please, reopen, if this bug is still reproducable
on the latest update of your distribution.

[This is mass-closing of bugs which seem to be too old and irrelevant anymore;
we are sorry, if we are closing your bug in mistake; please, don't hesitate to
reopen, if it is still alive issue.]

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