Bug#1023149: marked as done (pandoc FTBFS on i386)

2022-12-02 Thread Adrian Bunk
On Fri, Nov 25, 2022 at 10:31:01AM -0700, John MacFarlane wrote: > Just an observation: adding the -O0 option here will create an unoptimized > build, which will run more slowly. So this is definitely not a patch that > should remain more than short-term. >... That's clear, but it is only on i3

Bug#1023149: marked as done (pandoc FTBFS on i386)

2022-11-25 Thread John MacFarlane
Just an observation: adding the -O0 option here will create an unoptimized build, which will run more slowly. So this is definitely not a patch that should remain more than short-term. I have no idea what this issue is, by the way. We regularly test pandoc upstream against ghc versions 8.6.5,

Bug#1023149: marked as done (pandoc FTBFS on i386)

2022-11-24 Thread Debian Bug Tracking System
Your message dated Thu, 24 Nov 2022 08:37:07 + with message-id and subject line Bug#1023149: fixed in pandoc 2.17.1.1-1.1 has caused the Debian Bug report #1023149, regarding pandoc FTBFS on i386 to be marked as done. This means that you claim that the problem has been dealt with. If this is