[libvoikko] HFST support to libvoikko in Debian and Ubuntu?

[Timo Jyrinki]

2016-02-26 6:38 GMT+02:00 Kartik Mistry <kartik at debian.org>:
> On Thu, Feb 25, 2016 at 11:34 PM, Timo Jyrinki <timo.jyrinki at gmail.com> wrote:
>> When hfst-ospell is uploaded to unstable, I will likewise follow with
>> another libvoikko upload to unstable.
>
> ^^ Tino, should I do that? Let me know!

Ubuntu 16.10 is open for development, and hfst-ospell is in there [1].
On the Debian side, we managed to get hfst-ospell migrate to Debian
testing and likewise the new libvoikko with HFST support migrated to
testing. That means they will be included in the next Debian release.
The next steps might be dictionaries and including support in default
installations for various languages (in addition to Finnish that is
already done).

[1] https://launchpad.net/ubuntu/+source/hfst-ospell

However, getting hfst-ospell to build properly required the tests to
be disabled by Kartik/Tino [2]. For Ubuntu to get new libvoikko,
hfst-ospell as a new runtime dependency would need to go to Main
Inclusion Process [3], for which one of the requirements [4] is
executing the available tests. Would there anyone from for example
University of Helsinki side who could work on resolving the test
issues if they are general issues so they could be re-enabled? Or if
it's Debian build environment specific, maybe more debugging there
would be needed? For example (just an example), would the tests expect
UTF locale that should be set during tests, or some other
requirements?

[2] https://anonscm.debian.org/cgit/debian-science/packages/hfst-ospell.git/commit/?id=ee4316d9bda6eef51abfcff2a820818967770546
[3] https://wiki.ubuntu.com/MainInclusionProcess
[4] https://wiki.ubuntu.com/UbuntuMainInclusionRequirements

Until then, Ubuntu will be stuck with the old libvoikko version [5]
and without HFST support, because I can't sync the new libvoikko from
Debian before hfst-ospell has gone through the main inclusion process.

[5] https://launchpad.net/ubuntu/+source/libvoikko

I can handle the process itself, but I don't want to start that while
there are existing known blockers. I think the tests enablement would
be the only one.

-Timo