Bug 342581

Summary:	multiarch conflicts in mecab
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	mecab	Assignee:	Mamoru TASAKA <mtasaka>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	rvokal
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-25 14:29:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bill Nottingham 2007-10-19 21:50:52 UTC

mecab (or one of its subpacakges) has multiarch conflicts when installed for both i386 and x86_64 in the Fedora development tree. For help in resolving them, see http://fedoraproject.org/wiki/PackagingDrafts/MultilibTricks. 

  file /etc/mecabrc from install of mecab-0.96-1.fc8.2 conflicts with file from package mecab-0.96-1.fc8.2
  file /usr/bin/mecab-config from install of mecab-devel-0.96-1.fc8.2 conflicts with file from package mecab-devel-0.96-1.fc8.2

(Note that this is an automated bug filing.)
It would be nice to have these bugs fixed by the beta of Fedora 9.

Comment 1 Bill Nottingham 2007-10-22 20:07:14 UTC

This should be fixed, whether by changing the files or changing the packaging.

Comment 2 Mamoru TASAKA 2007-10-23 01:58:42 UTC

Please don't expect that mecab(-devel) can be multi-arch installable.

Comment 3 Bill Nottingham 2007-10-23 17:17:38 UTC

Why not? Hundreds of other apps are.

Comment 4 Mamoru TASAKA 2007-10-23 17:30:06 UTC

Similar with hyperestraier, mecab reads text files and creates/reads
something like database files, which are *arch dependent*.

So, for example if 
- a package using 32 bit mecab library creates some files
- and another package using 64 bit mecab library reads the files
it is hazardous. So generally mecab isn't multiarch installable.

Comment 5 Bill Nottingham 2007-10-23 17:38:45 UTC

However, we install devel as multiarch so things can build against the devel
libraries - how does that prevent this?

Comment 6 Mamoru TASAKA 2007-10-23 17:47:12 UTC

First,
- I cannot figure out why you want to install two arch devel packages
  even if mecab libraries are not multiarch installable.
  Any strong rationale, approved by packaging committee?

Comment 7 Mamoru TASAKA 2007-10-23 17:52:56 UTC

Moreover, /usr/bin/mecab-config contains the information of
the data used by mecab library installed, not just pointing the
place of the libraries or else.

Comment 8 Mamoru TASAKA 2007-10-25 14:29:52 UTC

So I cannot find out any ratiorate for fixing multiarch conflict
even if mecab does not expect multiarch install.

Closing as WONTFIX again for now.

- Please discuss what we should fix for what purpose on some mailing
  list first.