Bug 16479

Summary: m17n-contrib-1.1.14-6.mga5.noarch conflicts with file from package m17n-db-1.6.5-4.mga5.noarch
Product: Mageia Reporter: Jim Beard <jim.beard>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: marja11
Version: 5   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: m17n-contrib-1.1.14-6.mga5.noarch m17n-db-1.6.5-4.mga5.noarch CVE:
Status comment:

Description Jim Beard 2015-07-26 18:00:43 CEST
Description of problem: An attempt to install m17n-contrib-1.1.14-6.mga5.noarch using urpmi results in:


[root@localhost bin]# urpmi m17n-contrib
http://mageia.jameswhitby.net/mageia/distrib/5/x86_64/media/core/release/m17n-contrib-1.1.14-6.mga5.noarch.rpm
installing m17n-contrib-1.1.14-6.mga5.noarch.rpm from /var/cache/urpmi/rpms
Preparing...                     #############################################
Installation failed:    file /usr/share/m17n/as-inscript.mim from install of m17n-contrib-1.1.14-6.mga5.noarch conflicts with file from package m17n-db-1.6.5-4.mga5.noarch
        file /usr/share/m17n/bn-probhat.mim from install of m17n-contrib-1.1.14-6.mga5.noarch conflicts with file from package m17n-db-1.6.5-4.mga5.noarch
        file /usr/share/m17n/ml-inscript.mim from install of m17n-contrib-1.1.14-6.mga5.noarch conflicts with file from package m17n-db-1.6.5-4.mga5.noarch
        file /usr/share/m17n/ml-mozhi.mim from install of m17n-contrib-1.1.14-6.mga5.noarch conflicts with file from package m17n-db-1.6.5-4.mga5.noarch
        file /usr/share/m17n/or-inscript.mim from install of m17n-contrib-1.1.14-6.mga5.noarch conflicts with file from package m17n-db-1.6.5-4.mga5.noarch
        file /usr/share/m17n/sa-iast.mim from install of m17n-contrib-1.1.14-6.mga5.noarch conflicts with file from package m17n-db-1.6.5-4.mga5.noarch
        file /usr/share/m17n/te-inscript.mim from install of m17n-contrib-1.1.14-6.mga5.noarch conflicts with file from package m17n-db-1.6.5-4.mga5.noarch
        file /usr/share/m17n/yi-yivo.mim from install of m17n-contrib-1.1.14-6.mga5.noarch conflicts with file from package m17n-db-1.6.5-4.mga5.noarch


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


How reproducible: as root, run command urpmi  m17n-contrib-1.1.14-6.mga5.noarch

Steps to Reproduce:
1.
2.
3.

So far, I have the ibus engine running and have been able to enter Vietnamese in an mlterm window.  I have not been able to enter Vietnamese using gedit which used to be my preferred editor for vi,nor have I been able to enter Japanese or Chinese (anthy, libpinyin) but experimentation continues.


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2015-07-28 20:13:27 CEST

Assignee: bugsquad => fundawang

Comment 1 Marja Van Waes 2018-04-14 11:59:15 CEST
Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change it's status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

(In case this report needs to stay open for a supported release: Reassigning to all packagers collectively, since there is no longer a registered maintainer for this package.)

Assignee: fundawang => pkg-bugs
CC: (none) => marja11

Comment 2 Marja Van Waes 2018-10-07 15:09:59 CEST
No reply, so closing as OLD since Mageia 5 is no longer maintained.

Resolution: (none) => OLD
Status: NEW => RESOLVED