Hi Emmanuel On 01-05-2021 14:43, Emmanuel Bourg wrote: > Every time OpenJDK is > updated in Debian, the corresponding DCEVM package has to be updated as > well, otherwise it's likely to fail or crash. That's exactly what > happens currently in testing, we have OpenJDK 11.0.11 with DCEVM > 11.0.10, and DCEVM just crashes (a simple invocation of "java -dcevm > -version" throws an error). But OpenJDK 11.0.11 was uploaded two months ago, when we were still in the soft freeze. Why didn't you fix openjdk-11-jre-dcevm then? 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. How do you normally get triggered to update you package? > I agree the diff is not reviewable, but it can be seen as an update of > the DCEVM code to the same state as the OpenJDK code that was already > accepted in testing. Two months ago, in a different stage of the release. Paul
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature