Package: dh-autoreconf Version: 13 Severity: normal dh-autoreconf Depends on automake | automaken. On all buildds except experimental, the first alternative is preferred, and builds will happen with the current (highest available) version of automake, currently 1.15 in stretch and 1.14.1 in jessie.
Unfortunately, the aspcud resolver used for experimental buildds does not assign a lower score to less-preferred alternatives, in this case packages that provide automaken. The result is that about half the time automake1.11 is chosen instead. Upstreams do not typically test with such old versions, even if their packages are theoretically meant to work with them, and the typical result is a FTBFS (or, worse, a silent mis-build). flatpak 0.8.4-1 is a good example. Its configure.ac claims to work with automake1.11, but in fact it doesn't: https://buildd.debian.org/status/logs.php?pkg=flatpak&ver=0.8.4-1&suite=experimental So far I've worked around this in flatpak, glib2.0 and ostree by explicitly build-depending on automake, but there are probably lots more packages affected, and I think it would be better to address this globally by changing dh-autoreconf's dependency. (I'm also going to open a buildd.debian.org bug to investigate whether the aspcud rules can be adjusted to prefer or even require the most-preferred alternative.) S
