Bug#978377: apertium-eo-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)

[Lucas Nussbaum]

Source: apertium-eo-fr
Version: 0.9.0~r57551-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<<PKGBUILDDIR>>'
> apertium-validate-dictionary apertium-eo-fr.fr.dix
> apertium-eo-fr.fr.dix:4195: element pardef: Schemas validity error : Element 'pardef': Duplicate key-sequence ['fa/illir__vblex'] in unique identity-constraint 'pardef-unique'.
> apertium-eo-fr.fr.dix:6615: element pardef: Schemas validity error : Element 'pardef': Duplicate key-sequence ['épou/x__n'] in unique identity-constraint 'pardef-unique'.
> lt-comp lr apertium-eo-fr.fr.dix fr-eo.automorf.bin apertium-eo-fr.fr.acx
> apostrophes at postblank 3758 5345
> final at inconditional 69 424
> main at standard 92977 155700
> negations at standard 35117 49188
> negations_apost at postblank 3334 4708
> unstandard_orth at standard 4572 6896
> unstandard_orth_apost at postblank 139 180
> apertium-validate-dictionary apertium-eo-fr.eo-fr.dix
> lt-comp rl apertium-eo-fr.eo-fr.dix fr-eo.autobil.bin
> Error: Invalid dictionary (hint: entry on the right beginning with whitespace)
> make[2]: *** [Makefile:783: fr-eo.autobil.bin] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/apertium-eo-fr_0.9.0~r57551-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.