Le 03/05/2021 à 10:15, Emmanuel Bourg a écrit : >> If your package is so tightly tied to the version of openjdk I would >> expect mechanisms to be in place to warn you of the upload and to prevent >> migration of openjdk-11 in case of breakage. E.g. autopkgtest is very >> well suited to prevent the migration because it's integrated with our >> migration software. Having an autopkgtest has the additional benefit >> that at this stage of the release, you're package isn't blocked if it >> passes on all architecture and you wouldn't need to bother us with an >> unblock request. > > I agree that a better QA mechanism would be good. I'd be a bit reluctant > to implement autopkgtest though, my understanding is that openjdk-11 > would be blocked from migrating if it breaks openjdk-11-jre-dcevm, but > if DCEVM upstream lags to rebase its patches that would be unfair to > delay the OpenJDK update, because OpenJDK has a much larger user base > than DCEVM and the benefits of an OpenJDK update outweigh a temporary > breakage of DCEVM.
I've noticed that openjdk-11 already has two autopkgtest failures reported and they seem to be ignored. So I went ahead and uploaded openjdk-11-jre-dcevm/11.0.11+9-2 with a simple autopkgtest test suite that should catch similar failures in the future. Emmanuel Bourg
