Re: Getting hunspell 1.7.2 into unstable

Hi, Am 18.06.23 um 13:49 schrieb Changwoo Ryu: 2023년 6월 18일 (일) 오후 8:00, Rene Engelhard 님이 작성: Should I add a Breaks: hunspell-ko (<< 0.7.94) here? Strictly speaking it's not needed since it's a test failing not the dict being unusable, but we could go the "better safe than sorry" route

Re: Getting hunspell 1.7.2 into unstable

2023년 6월 18일 (일) 오후 8:00, Rene Engelhard 님이 작성: > > >> Should I add a Breaks: hunspell-ko (<< 0.7.94) here? Strictly speaking > >> it's not needed since it's a test failing not the dict being unusable, > >> but we could go the "better safe than sorry" route anyways. > > No need. The problem still

Re: Getting hunspell 1.7.2 into unstable

Hi, Am 18.06.23 um 12:52 schrieb Changwoo Ryu: 2023년 6월 18일 (일) 오후 7:39, Rene Engelhard 님이 작성: But I saw you uploaded hunspell-dict-ko 0.7.94 which incidentally has someting hunspell 1.7.2-related (did I mention I don't like the stuff being in Korean instead of English). At least the tests

Re: Getting hunspell 1.7.2 into unstable

2023년 6월 18일 (일) 오후 7:39, Rene Engelhard 님이 작성: > > But I saw you uploaded hunspell-dict-ko 0.7.94 which incidentally has > someting hunspell 1.7.2-related (did I mention I don't like the stuff > being in Korean instead of English). > > At least the tests pass with hunspell 1.7.2 and

Re: Getting hunspell 1.7.2 into unstable

Hi, Am 13.06.23 um 18:49 schrieb Rene Engelhard: Am 12.06.23 um 19:32 schrieb Changwoo Ryu: This failure is not from hunspell-dict-ko. hunspell just failed to call iconv() in that environment. Yeah, see  the code point in question, just wondering how that happens. Probably because of the

Re: Getting hunspell 1.7.2 into unstable

Hi, Am 12.06.23 um 19:32 schrieb Changwoo Ryu: This failure is not from hunspell-dict-ko. hunspell just failed to call iconv() in that environment. Yeah, see  the code point in question, just wondering how that happens. Probably because of the minimal (buildd) chroot, works in my full

Re: Getting hunspell 1.7.2 into unstable

2023년 6월 13일 (화) 오전 2:23, Rene Engelhard 님이 작성: > I'd try whether current git has some fixes in it but then I still get > into the same issue as I think I outlined once: > > rene@frodo:~/hunspell-dict-ko-0.7.93$ make hosttest > HOST_DICT_PATH=/usr/share/hunspell/ko > make -C tests test

Re: Getting hunspell 1.7.2 into unstable

Hi, Am 12.06.23 um 18:58 schrieb Changwoo Ryu: 2023년 6월 11일 (일) 오후 7:34, Rene Engelhard 님이 작성: This blocks (well, theoretically not, but then it'd block in unstable) the upload of hunspell 1.7.2 which has many bugfixes and improvements (and which the new version of r-cran-hunspell - due to

Re: Getting hunspell 1.7.2 into unstable

Hi, 2023년 6월 11일 (일) 오후 7:34, Rene Engelhard 님이 작성: > > This blocks (well, theoretically not, but then it'd block in unstable) > the upload of hunspell 1.7.2 which has many bugfixes and improvements > (and which the new version of r-cran-hunspell - due to embedding > internal headers - also needs

Getting hunspell 1.7.2 into unstable

Hi, I think I pointed that out when hunspell 1.7.2+really1.7.2-4 was out and the test results came in. Might be overseen or simply postponed due to the (upcoming) freeze anyways. Let's have a try at it again :) the experimental pseudo-excuses for hunspell say: Experimental: Pseudo-Excuse