Bug 158778

Summary: secondary language packages are not installed
Product: [openSUSE] SUSE Linux 10.1 Reporter: Andreas Klein <asklein>
Component: YaST2Assignee: Ladislav Slezák <lslezak>
Status: RESOLVED DUPLICATE QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: hi-du, jsuchome, vetter
Version: Beta 8   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: YaST2 logs of affected system

Description Andreas Klein 2006-03-16 19:54:53 UTC
I installed the system with German as secondary language, but there are no ispell, aspell. Ooo packages for the german language installed.
Comment 1 Andreas Jaeger 2006-04-05 20:41:37 UTC
Christoph, can you confirm whether this still exists?
Comment 2 Christoph Thiel 2006-04-06 13:27:05 UTC
I was unable to reproduce with Build 905 on x86_64. Closing WORKSFORME.
Comment 3 Christoph Thiel 2006-04-06 13:28:20 UTC
*** Bug 159406 has been marked as a duplicate of this bug. ***
Comment 4 Rebecca Walter 2006-07-10 13:10:53 UTC
Created attachment 93039 [details]
YaST2 logs of affected system
Comment 5 Rebecca Walter 2006-07-10 13:14:03 UTC
I just encountered this installing with Danish as a secondary language.  Logs are already attached.  Adding jsuchome to CC because I discussed this issue with him before reporting.
Comment 6 Jiří Suchomel 2006-07-10 13:57:08 UTC
AFAIK this was already fixed for SLES10 (I just tested it and it worked) and the problem remains in 10.1. Workaround: it seems to work when you (after selecting secondary language) enter the Package Selection in the installation proposal and confirm the dialog (no need to select anything there).

Lada, could you comment in which version of pkg-bindings was this fixed? Is there any way we could fix this for box? (I doubt...)
Comment 7 Ladislav Slezák 2006-07-10 14:14:59 UTC
It was fixed in yast2-pkg-bindings-2.13.84.

It should be fixed in SLES10, but there is no way to fix it in 10.1. The only way would be a driver update (service pack), but it is issued only for maintained products...

So it will be fixed in 10.2 release.

*** This bug has been marked as a duplicate of 172223 ***