Bug#896109: flif FTBFS: bouncing-ball-frame01.png is not the same image as decoded-test-frame-000.pam

Control: severity -1 important On Fri, Apr 20, 2018 at 10:22:15AM +0200, Paride Legovini wrote: >... > How did you reproduce it on amd64? It always complies fine here. > Reproducing on amd64 would greatly simplify the debugging. This was actually my fault. What I actually got was a different err

Bug#896109: flif FTBFS: bouncing-ball-frame01.png is not the same image as decoded-test-frame-000.pam

The package also compiles fine in my local sbuild environment and on debomatic-amd64: http://debomatic-amd64.debian.net/distribution#unstable/flif/0.3-1/buildlog Paride

Bug#896109: flif FTBFS: bouncing-ball-frame01.png is not the same image as decoded-test-frame-000.pam

Control: forwarded 896109 https://github.com/FLIF-hub/FLIF/issues/498 On Thu, 19 Apr 2018 17:34:44 +0300 Adrian Bunk wrote: > > flif FTBFS (also reproduced on amd64): > > https://buildd.debian.org/status/package.php?p=flif&suite=sid Dear Adrian, Thanks for your report. I noticed the issue and

Bug#896109: flif FTBFS: bouncing-ball-frame01.png is not the same image as decoded-test-frame-000.pam

Source: flif Version: 0.3-1 Severity: serious flif FTBFS (also reproduced on amd64): https://buildd.debian.org/status/package.php?p=flif&suite=sid ... + check ../tools/bouncing_ball_frames/ decoded-test-frame-000.pam decoded-test-frame-001.pam decoded-test-frame-002.pam decoded-test-frame-003.