Bug 4326

Summary: 2_a3: myspell-en_GB <= 1.0.2-30 is obsoleted by (installed) hunspell-en
Product: Mageia Reporter: Bit Twister <bittwister2>
Component: RPM PackagesAssignee: Kamil Rytarowski <n54>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: anssi.hannula
Version: CauldronKeywords: Triaged
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: hunspell-en CVE:
Status comment:
Attachments: urpmi --debug myspell-en_GB results
rpm -qa results

Description Bit Twister 2012-01-29 02:35:50 CET
Description of problem:

installing myspell-en_GB-1.0.2-30.mga1.noarch.rpm from /var/cache/urpmi/rpms
Installation failed:    myspell-en_GB <= 1.0.2-30 is obsoleted by (installed) hunspell-en-0.20110318.1-2.mga2.noarch


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


How reproducible:


Steps to Reproduce:
1. boot boot-nonfree.iso
2. clean ftp network install

Note: package install failure
Comment 1 Manuel Hiebel 2012-01-29 11:49:18 CET
Can you run urpmi with --debug ? to see why it's failed ?
Comment 2 Bit Twister 2012-01-29 16:17:49 CET
Created attachment 1456 [details]
urpmi --debug myspell-en_GB results
Comment 3 Manuel Hiebel 2012-01-30 01:23:38 CET
Ah yes sorry this is useless 

We will remove myspell and co for the mga 2. added the maintainer of hunspell

Keywords: (none) => Triaged
Component: Installer => RPM Packages
Source RPM: (none) => hunspell-en

Manuel Hiebel 2012-01-30 01:26:45 CET

Assignee: bugsquad => n54

Comment 4 Kamil Rytarowski 2012-01-30 02:36:13 CET
Hello Bit!

Myspell dictionaries are obsoleted and replaced by Hunspell ones. There is included a backward-compatibily - the dictionaries are installed into /usr/myspell/ and the Obsoletes&Provides are set to rename the myspell dicts.

More info:
https://wiki.mageia.org/en/Hunspell-dictionary_policy

How are you experiencing this error? Are you selecting myspell-dicts manually? Or it is breaking a clean installation?
Comment 5 Bit Twister 2012-01-30 03:13:18 CET
(In reply to comment #4)
> Hello Bit!

Hi.

> How are you experiencing this error? Are you selecting myspell-dicts manually?
> Or it is breaking a clean installation?

As test procedure indicates it is a clean install.
Not selecting myspell manually. I just pick KDE, Development and all servers in the custom package selection screen.

It is not "breaking" a clean install. but the error should not show up.

I have no idea what the ramifications of dangling links might cause, see 
bug 43380
Comment 6 Kamil Rytarowski 2012-01-30 03:51:45 CET
Attach please a result of "rpm -qa".

Status: NEW => ASSIGNED

Comment 7 Bit Twister 2012-01-30 04:24:44 CET
Created attachment 1462 [details]
rpm -qa results
Comment 8 Kamil Rytarowski 2012-01-30 18:04:34 CET
I have not reproduced it. I can see myspell dicts on your list.. something is forcing it to install. I will keep migrating the other dicts and then test it in Beta1.
Comment 9 Kamil Rytarowski 2012-02-02 12:23:28 CET
I've installed Cauldron from boot-iso:

$ rpm -qa|grep csb
myspell-csb_CSB-1.0.2-30.mga1
hunspell-csb-0.20050311.1-7.mga2

$ urpmq --provides myspell-csb_CSB
myspell-pl[== 1.0.2-30.mga1]
myspell-dictionary[== 1.0.2-30.mga1]
enchant-dictionary[== 2]
myspell-csb_CSB[== 1.0.2-30.mga1]

$ urpmq --provides hunspell-csb
enchant-dictionary[== 2]
hunspell-dictionary
hunspell-csb_PL[== 0.20050311.1-7.mga2]
dictionary-csb[== 2]
dictionary-csb_PL[== 2]
myspell-csb
myspell-csb_CSB
hunspell-csb[== 0.20050311.1-7.mga2]


$ urpmq --obsoletes hunspell-csb
myspell-csb[<= 1.0.2-30]
myspell-csb_CSB[<= 1.0.2-30]

Anssi could you help please? Why hunspell-csb isn't obsoleting myspell-csb_CSB?

CC: (none) => anssi.hannula

Comment 10 Kamil Rytarowski 2012-02-12 22:06:36 CET
I have made corrections in hunspell-en. Please check now.
Comment 11 Bit Twister 2012-02-13 01:42:37 CET
I will re-test on the Beta 1 dvd install.

FTP network installs will not complete before ftp site decides I have been connected far too long and breaks the connection. Having to do that over and over to finally get an install does not give me a warm felling that the install is really completed without causing weird rpm problems.
Comment 12 Kamil Rytarowski 2012-02-13 03:43:47 CET
There was also fixed bug #4502. I hope it will be resolved completely.
Comment 13 Bit Twister 2012-02-22 18:17:05 CET
clean beta1 install does not have the problem.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED