On Fri, 5 Feb 2021 at 23:51, Mario Blättermann <mario.blaetterm...@gmail.com> wrote:
> Hello Javier, > > as Helge already wrote, manpages-es-extra is far too outdated to worth > shipping it in Bullseye. It is *now* the time to get rid of this > package. > Indeed, this is the case I have opened Bug #984734 today to request this. Sorry for the delay as this should have been done a long time ago already. > Tomorrow we will release a new version of manpages-l10n, which will > contain Spanish translations for the first time, after manpages-es > vanished from Debian (for good reasons). I'm almost finished with the > import of the plain text translations from manpages-es-extra, so I > think the .po files will be available for translators a few days after > the upcoming release. This means in return: Because manpages-l10n > doesn't distinguish between »es« and »es-extra« files, the release in > march will include the newly imported .po files – and raise file > conflicts. I think you agree with me that it's better to have 100 .po > files (at least 80% translated) which are up-to-date than 200 terribly > outdated plain text translations which nobody benefits of. > I fully agree with this approach and would suggest you. To fix the file conflicts I guess you could add a Conflicts with older versions of manpages-es-extra. Would it make sense to have a transitioning (dummy) package to have users migrate from manpages-es-extra to manpages-l10n? That way users with the manpages-es-extra package installed (for whatever reason, but maybe because it was at some point pulled in because 'manpages-es' was in the Spanish task selection) would pull in automatically manpages-l10n. Best regards Javier
