| Summary: | calligra badly breaks upgrading mga5 to mga6 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thierry Vignaud <thierry.vignaud> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | release_blocker | CC: | mageia, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | calligra-3.0.0.1-1.mga6.x86_64 | CVE: | |
| Status comment: | |||
| Attachments: | the full conflicts breakage upgrade logs | ||
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 Created attachment 8902 [details]
the full conflicts breakage upgrade logs
Marja Van Waes
2017-01-29 10:07:17 CET
CC:
(none) =>
marja11 thank you, i will look to this Status:
NEW =>
ASSIGNED I fixed it in calligra-3.0.0.1-3.mga6. Status:
ASSIGNED =>
RESOLVED |
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...