Thank you, but I'm still completely lost here. :) Can we retry the pandoc armel build to verify if it's a fluke or a bug to report upstream? How can be find other such problems (because it seems to me there are many not listed on the page you mentioned)?
On Sun, Jul 29, 2018 at 9:18 AM, Clint Adams <[email protected]> wrote: > On Mon, Jul 23, 2018 at 11:27:59PM +0200, Mikolaj Konarski wrote: >> it says "Migrates after haskell-vector/amd64..." >> so I thought it's waiting for the BinNMU to succeed. Is it? > > Take a look at https://release.debian.org/transitions/html/haskell.html > > Your problem might be that pandoc binNMU failed on armel[0], preventing > hakyll from being built, preventing vector from migrating, which also > prevents lambdahack from migrating.. or something like that. > > [0] > https://buildd.debian.org/status/fetch.php?pkg=pandoc&arch=armel&ver=2.2.1-2%2Bb1&stamp=1531571285&raw=0
