On 12/3/18 8:59 AM, Ole Streicher wrote: >>> autopkgtests for 0.9.9-1 still fail [0], and since it's blocking the >>> migration of hdf5 it makes the package unsuitable for release >>> justifying the RC severity [1]. >> >> Sorry, but I don't see this: gdl does not *break* hdf5 ("break" means >> IMO that a package that worked before does not work anymore -- but hdf5 >> still works nicely, right?), and it also does not block the transition. >> >> As far as I know, CI tests are currently setup in a non-blocking way. >> And when I look into the maintainer page of hdf5, it says >> >> "Required age increased by 30 days because of autopkgtest". >> >> This is not a block, this is just a delay. There never was a statement >> that failing CI tests are RC (or would become so before buster). >> >> So, you you please be a bit more explicit how the RC policy applies here?
hdf5 is unable to migrate to testing because gnudatalanguage autopkgtests fail. Test failures indicate that the package is broken, and not suitable for release. It should be removed from testing until the test failures are fixed, which also allows hdf5 and its rdeps to migrate to testing. As announced the autopkgtest delay is increased exponentially which will block packages from getting into buster before the final freeze. We do not want that to happen, but your package is not allowing hdf5 and its rdeps to migrate even though there is nothing else preventing this part of the transition. Fix your failing autopkgtests or remove them. Not fixing failing autopkgtests in your package that prevent its dependencies from (timely) testing migration is very unfriendly (to phrase it very mildly). Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1