Bug#978364: apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty)
On Sun, Jan 31, 2021 at 11:20 PM Tino Didriksen wrote: > I did CC Kartik in the original mail. I assume it was lost in the crowd. > https://salsa.debian.org/science-team/apertium-rus-ukr is up-to-date and > bundled and is the only thing that wanted apertium-ukr, so after > apertium-rus-ukr is uploaded, apertium-ukr will be superfluous and should be > removed. Hi all, It seems that we had no rus-ukr pair in Debian :/ Uploading it now and hoping it will make it in the archive in time. -- Kartik Mistry | કાર્તિક મિસ્ત્રી kartikm.wordpress.com
Bug#978364: apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty)
I did CC Kartik in the original mail. I assume it was lost in the crowd. https://salsa.debian.org/science-team/apertium-rus-ukr is up-to-date and bundled and is the only thing that wanted apertium-ukr, so after apertium-rus-ukr is uploaded, apertium-ukr will be superfluous and should be removed. -- Tino Didriksen On Sun, 31 Jan 2021 at 18:33, Nilesh Patra wrote: > Hi Tino, > > On Tue, 5 Jan 2021 01:13:56 +0100 Tino Didriksen > wrote: > > apertium-ukr should be removed from Debian. The pair that needed it has > > been upgraded to bundle the required version instead: > > If you agree, can I retitle and reassign to file in a removal bug for > apertium-ukr, then? > Also, I do not see apertium-rus-ukr at either the archive or the tracker - > did this not get uploaded, yet? > > Nilesh
Bug#978364: apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty)
Hi Tino, On Tue, 5 Jan 2021 01:13:56 +0100 Tino Didriksen wrote: > apertium-ukr should be removed from Debian. The pair that needed it has > been upgraded to bundle the required version instead: If you agree, can I retitle and reassign to file in a removal bug for apertium-ukr, then? Also, I do not see apertium-rus-ukr at either the archive or the tracker - did this not get uploaded, yet? Nilesh
Bug#978364: apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty)
apertium-ukr should be removed from Debian. The pair that needed it has been upgraded to bundle the required version instead: https://salsa.debian.org/science-team/apertium-rus-ukr -- Tino Didriksen
Bug#978364: apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty)
Source: apertium-ukr Version: 0.1.0~r82563-2 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[1]: Entering directory '/<>' > apertium-validate-dictionary apertium-ukr.ukr.dix > /bin/mkdir -p .deps > lt-comp lr apertium-ukr.post-ukr.dix ukr.autopgen.bin > /usr/bin/cg-comp apertium-ukr.ukr.rlx ukr.rlx.bin > touch .deps/.d > apertium-validate-modes modes.xml > main@standard 6 14 > apertium-validate-dictionary apertium-ukr.ukr.dix > Sections: 1, Rules: 29, Sets: 67, Tags: 138 > 10 rules cannot be skipped by index. > apertium-gen-modes modes.xml > lt-comp lr apertium-ukr.ukr.dix ukr.automorf.bin apertium-ukr.ukr.acx > lt-comp rl apertium-ukr.ukr.dix ukr.autogen.bin apertium-ukr.ukr.acx > final@inconditional 34 301 > gci@standard 583 789 > main@standard 16515 38654 > lt-print ukr.autogen.bin | gzip -9 -c -n > ukr.autogen.att.gz > Error: Invalid dictionary (hint: the left side of an entry is empty) > make[1]: *** [Makefile:729: ukr.automorf.bin] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/12/26/apertium-ukr_0.1.0~r82563-2_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.
