On Tue, Mar 26, 2019 at 07:29:12PM +0100, Gert Wollny wrote: > the problem is I at least don't know the offending package because I > was not able to reproduce the build failure. Whatever it was, it has > probably already benn fixed.
My build history for buster: Status: successful gdcm_2.8.8-5_amd64-20181230T191455.669Z Status: successful gdcm_2.8.8-5_amd64-20190114T071348.822Z Status: successful gdcm_2.8.8-6_amd64-20190124T082314.888Z Status: failed gdcm_2.8.8-6_amd64-20190205T224359.890Z Status: failed gdcm_2.8.8-6_amd64-20190219T002627.991Z Status: failed gdcm_2.8.8-6_amd64-20190302T232244.473Z Status: failed gdcm_2.8.8-6_amd64-20190304T231307.933Z Status: successful gdcm_2.8.8-6_amd64-20190321T073112.209Z This means the buggy build-depends (some texlive package, I suppose) entered testing somewhere between 20190124 and 20190205 and the fixed package entered testing somewhere between 20190304 and 20190321. If this information is not enough to determine which one it was, feel free to close the bug. Thanks.