Bitrotted released pairs (summer 2022)

[TinoDidriksen]

The lastest released version of these pairs no longer build for various reasons:

• apertium-cat-ita : Error (line 596): Invalid construction.
• apertium-dan-nor : apertium-nob.nob.rlx: Error: Expected set on line 5830 near )␊;␊# "verken ... e!
• apertium-fra-cat : Error (line 229): Invalid construction.
• apertium-fra-frp : Error at line 4615, column 23: Undefined attr-item lemg.
• apertium-nno-nob : apertium-nob.nob.rlx: Error: Expected set on line 5830 near )␊;␊# "verken ... e!
• apertium-oci-fra : Error at line 4327, column 66: Undefined attr-item lemg.
• apertium-por-cat : Error (line 632): Invalid construction.
• apertium-swe-nor : apertium-nob.nob.rlx: Error: Expected set on line 5830 near )␊;␊# "verken ... e!

Ping @hectoralos @unhammer

[hectoralos]

I am not sure what the errors are in the three Catalan-related pairs. I have found and corrected syntax errors in cat-ita (apparently, new versions of the compilers are stricter, which is to be welcomed). But I have not found anything of the kind in fra-cat or por-cat.

[TinoDidriksen]

You shouldn't find anything in current HEAD of the repos. The point is that the listed pairs need new releases, because the current release has bitrotted.

[hectoralos]

Sorry, I can't understand. I don't know what are the HEAD of the repos, nor what "bitrotted" means. I just add words and programme rules. I understand absolutely nothing about the arcana of Apertium.

[TinoDidriksen]

For example, the latest release of apertium-cat-ita is https://github.com/apertium/apertium-cat-ita/releases/tag/v0.2.1 from 2019-11-20. That's what no longer builds, because the tools are now stricter.

There are 2 ways to fix that: Either patch the released tarball, or make a new release from current repository state. I would prefer a new release. So what I would like is for the relevant pair authors (which Github says is you and Unhammer) to sign off that current status is good enough, or to do minimal fixes to make current state good enough.

[hectoralos]

OK, thanks for the clarification. I'll prepare new releases, hopefully during the next week.

[unhammer]

Is there a deadline here for getting things into Debian? I'm going to be afk for most of July, so if it's before that then nno-nob/dan-nor could be tagged as they are (they're not completely consistent in the ->nno directions, but better than previous releases). Unfortunately swe->nno still has too many regressions (been too focused on nob->swe), so swe-nor would need a patch release if it has to happen during summer.

[TinoDidriksen]

Is there a deadline here for getting things into Debian?

The hard deadline is the Debian freeze starting on 2023-01-12, so there's no rush. It can wait the summer.

[hectoralos]

apertium-ita, apertium-cat-ita, apertium-por and apertium-por-cat are ready to be packed for a new release. With this, everything pending in this issue related to Catalan should be solved. (BTW, thanks for the packing of apertium-fra-cat, @TinoDidriksen )

[TinoDidriksen]

cat-ita and por-cat are now also released.

I've added apertium-fra-frp and apertium-oci-fra to the list of failures. I expect they just need to use latest released sources and verify that nothing broke.

[hectoralos]

Thanks for the releases, @TinoDidriksen .
As for apertium-fra-frp, I'll solve it in the next days. No problem.
But for apertium-oci-fra, there is a problem. It is, in fact, release-ready for several months, but I am collaborating with an institution. We have agreed that first they will present it publicly. They will do it on 14 October (if they don't delay it again, as they have done several times). After that we will be able to make our release. What the bug is, it's already been solved some time ago in the version on GitHub.

[unhammer]

• apertium-nno-nob: 3cfb292503f1b4ccf41c0db747ad3b70c92655e3 v1.5.0
  • apertium-nob: 8b75fddba5137405882afe72b0539c98075be7f3 v1.3.0
  • apertium-nno: 1054979a23978c6bd297271830c6efc75f4f492e v1.3.0

[hectoralos]

apertium-oci, apertium-frp, apertium-fra, apertium-oci-fra, and apertium-fra-frp are ready to be packed for a new release.

[TinoDidriksen]

Unfortunately, new apertium-oci-fra doesn't pass tests. Do you want tests ignored?

[TinoDidriksen]

Nevermind, package oci-fra already ignores tests. As does fra-frp, but fra-frp passed them.

[hectoralos]

I thought I passed all the tests. I'll take a look. For me, this is quite pro forma, because I really don't take care about this whole stuff. It find it too complex to manage.

[hectoralos]

Yes, I think oci-fra can be released. The tests show several cases that are not working. They are not serious enough to stop creation of a release. I also see that there are things that had been assumed to be good but were not and are now fixed.

[unhammer]

• https://github.com/apertium/apertium-swe-nor/releases/tag/v0.4.0
• https://github.com/apertium/apertium-dan-nor/releases/tag/v1.5.0

both depend on the just-tagged commits of their monolingual dependencies

• https://github.com/apertium/apertium-dan/releases/tag/v0.7.0
• https://github.com/apertium/apertium-swe/releases/tag/v0.8.2
• https://github.com/apertium/apertium-nob/releases/tag/v1.4.0
• https://github.com/apertium/apertium-nno/releases/tag/v1.4.0