Bug#894159: OpenTTD, icu and ParagraphLayout

2018-05-01 Thread Matthijs Kooijman
Hi László, > > So you're saying I could upload OpenTTD now, and it will be recompiled > > with icu60 once that is uploaded to Sid? Or should I wait a few days? > Well, the transition update and _maybe_ the real start is hours soon. But > as I see, OpenTTD might be uploaded and built, installed a

Bug#894159: OpenTTD, icu and ParagraphLayout

2018-05-01 Thread GCS
On Mon, Apr 30, 2018 at 4:08 PM Matthijs Kooijman wrote: > So you're saying I could upload OpenTTD now, and it will be recompiled > with icu60 once that is uploaded to Sid? Or should I wait a few days? Well, the transition update and _maybe_ the real start is hours soon. But as I see, OpenTTD mi

Bug#894159: OpenTTD, icu and ParagraphLayout

2018-04-30 Thread Matthijs Kooijman
Hi László, > > First off: I have a pending new upstream version of OpenTTD that I'd > > like to upload, but I don't want to interfere with this transition. > > Should I hold it off, or do we expect that resolving these issues will > > take a while and should I just upload it now (and have it build

Bug#894159: OpenTTD, icu and ParagraphLayout

2018-04-29 Thread GCS
On Sun, Apr 29, 2018 at 10:27 PM Matthijs Kooijman wrote: > I'm the maintainer of the OpenTTD package, and stumbled on this bug > report, which refers to my package as the last user of the > ParagraphLayout API in icu. Indeed. That's why I need the icu-le-hb loop which seems to be a dying proje

Bug#894159: OpenTTD, icu and ParagraphLayout

2018-04-29 Thread Matthijs Kooijman
Hi folks, I'm the maintainer of the OpenTTD package, and stumbled on this bug report, which refers to my package as the last user of the ParagraphLayout API in icu. First off: I have a pending new upstream version of OpenTTD that I'd like to upload, but I don't want to interfere with this transit