Hi Lisandro, On 07-07-2019 16:16, Lisandro Damián Nicanor Pérez Meyer wrote: >> All autopkgtest failures considered RC for bullseye >> =================================================== >> >> From now on, all autopkgtest failures will be considered release-critical for >> bullseye. So if your package has failing autopkgtests, now is a good time to >> start looking for a fix > > Now this raises some questions for me. Now I maintain a (huge) library > (hello Qt!). I do an unstable upload and package A starts failing it's > autopkgtests. In this case: > > - How does this failure affects the uploaded library (imagine we have > a transition, as it will always be Qt's case due to private headers).
By default, the migration to testing will be blocked, exactly like we have been doing the last half year. > - What's expected from the maintainers of the library? It is expected that you communicate (e.g. via a bug report filed against both packages like I have been doing for over a year now, see examples on [1]) with the maintainers of the package to see why the test starts failing. Together, you should be able to work out which package needs to adapt. Either the autopkgtest found a real issue in your library which you need to fix, or the package needs to adapt to the new status of your library, either by fixing the package itself, or its autopkgtest. The migration of your library will be stalled to give the package time to be adapted. Of course that needs to happen within a reasonable amount of time, so if it takes to long, or you and the maintainers of the package can't agree on who should adapt what, contact the release team. Just to be clear, in case you got confused by it, if the package *already* fails in testing, it isn't a concern for packages that just trigger that autopkgtest, only for the package with the failing autopkgtest. I wonder if you were thinking of something else? If so, please elaborate. Paul [1] https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian...@lists.debian.org
signature.asc
Description: OpenPGP digital signature