On 2023-06-18 13:57:01 +0200, Rene Engelhard wrote:
Hi,
hunspell-dict-ko was fixed/worked around the issue (0.7.94-1) so we can do
this now.
As said it's a no-op for anything except r-cran-hunspell which also is
prepared in experimental together with hunspell itself.
I might add a libhunspell-private-dev package later when I figured out how
to best prevent this by adding a strict dependency there instead of
hardcoding it... But even without that it's better to not have a copy of
private headers in r-cran-hunspell.
Can I upload to unstable?
Please go ahead