Bug 456745 - kde-l10n-German-4.1.0-1.fc9 conflicts with kde-i18n-German-3.5.9-8.fc9
Summary: kde-l10n-German-4.1.0-1.fc9 conflicts with kde-i18n-German-3.5.9-8.fc9
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-l10n
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Kevin Kofler
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: KDE41
TreeView+ depends on / blocked
 
Reported: 2008-07-26 08:47 UTC by Sebastian Vahl
Modified: 2008-07-27 10:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-27 00:07:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Terminal output of file conflicts (15.49 KB, text/plain)
2008-07-26 08:47 UTC, Sebastian Vahl
no flags Details

Description Sebastian Vahl 2008-07-26 08:47:28 UTC
Description of problem:
I've downloaded the new KDE 4.1 rpms directly from koji. It seems that the 
kdepim translations are shipped in both, kde-l10n and kde-i18n (at least for 
the german translation). I've attached the output of rpm to identify the 
conflicting files.


Version-Release number of selected component (if applicable):
kde-l10n-German-4.1.0-1.fc9
kde-i18n-German-3.5.9-8.fc9kde-l10n-German-4.1.0-1.fc9

Comment 1 Sebastian Vahl 2008-07-26 08:47:28 UTC
Created attachment 312698 [details]
Terminal output of file conflicts

Comment 2 Kevin Kofler 2008-07-26 13:56:50 UTC
I sorta expected this. We're going to fix this ASAP (not just for German, but 
also for everything else, of course :-) ).

Comment 3 Kevin Kofler 2008-07-26 21:16:50 UTC
Fixing this now.

Comment 4 Kevin Kofler 2008-07-27 00:07:55 UTC
Fixed for Rawhide in kde-i18n-3.5.9-9.fc10. Fixed for F9 in 
kde-l10n-4.1.0-1.fc9.1.

Rex, that should be the last piece of the KDE 4.1.0 update, please replace the 
old 4.0.99 stuff with 4.1.0 ASAP.

Comment 5 Sebastian Vahl 2008-07-27 10:17:06 UTC
The above posted problems are fixed but a new one appeared: bug #456797


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