On Wed, 24 May 2017, Adrian Bunk wrote: > After retries the builds succeeded a few days later on the buildds. > > The reproducible builds [1] do unfortunately not contain any builds from > the relevant timespan, but based on the fact that the build never failed > there before or after I'll assume this was a transient failure that is > long gone.
Hello Adrian. My build history for this package: Status: successful gtk-vnc_0.6.0-2_amd64-20170520T121435Z Status: successful gtk-vnc_0.6.0-2_amd64-20170523T165859Z Status: failed gtk-vnc_0.6.0-3_amd64-20170524T113052Z Status: failed gtk-vnc_0.6.0-3_amd64-20170529T084121Z Status: failed gtk-vnc_0.6.0-3_amd64-20170602T095544Z Status: failed gtk-vnc_0.6.0-3_amd64-20170610T113822Z Status: failed gtk-vnc_0.6.0-3_amd64-20170615T123506Z This does not seem transient to me. Can you try again in stretch a few more times and share the results? I've also triggered a rebuild in reproducible-builds (for both stretch and unstable), but packages failing there do not always fail with sbuild and vice-versa. Thanks.
