Bug 20202 - calligra badly breaks upgrading mga5 to mga6
Summary: calligra badly breaks upgrading mga5 to mga6
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker major
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-29 09:25 CET by Thierry Vignaud
Modified: 2017-01-31 12:50 CET (History)
2 users (show)

See Also:
Source RPM: calligra-3.0.0.1-1.mga6.x86_64
CVE:
Status comment:


Attachments
the full conflicts breakage upgrade logs (5.18 KB, text/plain)
2017-01-29 09:39 CET, Thierry Vignaud
Details

Description Thierry Vignaud 2017-01-29 09:25:53 CET
Calligra causes a bunch of conflicts that break upgrading from mga5 to mga6.
See eg:

        file /usr/share/locale/fr/LC_MESSAGES/calligra-defaulttools.mo conflicts between attempted installs of de calligra-l10n-fr-2.9.11-1.mga6.noarch and calligra-core-12:3.0.0.1-1.mga6.x86_64

(see attached file for the full logs)

The issue is that we've the following requires on mga5:
lib64komain13 -> calligra-l10n -> eg: calligra-l10n-fr

And then, when one upgrades to mga5, everything break havoc because translations were merged back into calligra-core *without* obsoleting the old translation packages.
Actually they're in both the translation packages & the core package...
Comment 1 Thierry Vignaud 2017-01-29 09:37:52 CET
Actually we still have the old translation packages b/c of those missing obsoletes.
This was silently done in 3.0.0-1.mga6

Priority: Normal => release_blocker
CC: (none) => mageia

Comment 2 Thierry Vignaud 2017-01-29 09:39:19 CET
Created attachment 8902 [details]
the full conflicts breakage upgrade logs
Marja Van Waes 2017-01-29 10:07:17 CET

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 3 Nicolas Lécureuil 2017-01-29 16:27:18 CET
thank you, i will look to this

Status: NEW => ASSIGNED

Comment 4 Thierry Vignaud 2017-01-31 12:50:34 CET
I fixed it in calligra-3.0.0.1-3.mga6.

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


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