The man-pages-l10n package is outdated. Version 4.9.2 is available. Two notes: It introduces three new languages: »es«, »it« and »mk«. The »es« part replaces the current packages man-pages-es and man-pages-es-extra. The »it« part replaces man-pages-it. The »mk« part is completely new and doesn't replace anything. The packages psmisc-23.4 and procps-ng-3.3.17 contain translatable man pages which conflict with those in man-pages-*-4.2.0. We have removed the conflicting files upstream. Once the mentioned packages get updated in Cauldron, manpages-l10 packages need to be updated in return, to avoid the mentioned file conflicts.
Thank you for this authoritative prompt and information. Assigning to the Internationalisation Team.
Assignee: bugsquad => i18n-bugs
(In reply to Lewis Smith from comment #1) > Thank you for this authoritative prompt and information. > > Assigning to the Internationalisation Team. Nothing we can do. It's up to the packagers.
CC: (none) => yurchor
Assignee: i18n-bugs => pkg-bugsCC: (none) => fri
Done for Cauldron!
Status: NEW => RESOLVEDCC: (none) => geiger.david68210Resolution: (none) => FIXED
(In reply to David GEIGER from comment #3) > Done for Cauldron! Why not to do this for Mageia 8?
CC: (none) => ouaurelien
(In reply to Aurelien Oudelet from comment #4) > (In reply to David GEIGER from comment #3) > > Done for Cauldron! > > Why not to do this for Mageia 8? For creating the translation templates, we (the upstream maintainers) use packages from Cauldron. Building manpages-l10n for other Mageia versions makes only sense if the package versions differ that much. But if desired, we can introduce Mageia 8 as a new distribution in our project, to keep the translations in sync with the contents of the english man pages. Would also make sense for possible backport packages.