Bug#987658: unblock: openjdk-11-jre-dcevm/11.0.11+9-1
Hi Paul,
Le 02/05/2021 à 21:38, Paul Gevers a écrit :
> 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?
OpenJDK 11.0.11+3 was uploaded in February, but this wasn't a GA
release, OpenJDK 11.0.11 was only officially released two weeks ago [1].
DCEVM upstream tends to only track the official releases (I don't think
non GA releases of OpenJDK should ever be in testing but that's another
debate). So I was in a bind until April 27th when DCEVM was updated, one
week after the 11.0.11 GA release. And I filed this unblock request the
very same day.
> 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.
> How do you normally get triggered to update you package?
I scan my DDPO [2] every week and look for upstream updates.
> Two months ago, in a different stage of the release.
I understand this unblock request bends the rules and I'm really sorry
for that. But that's really the best I can do to serve our users. The
risk is limited since this is a minor update of a leaf package that
trades a totally broken version for a good one, so I thought it was
worth considering for an exception.
Emmanuel Bourg
[1] https://wiki.openjdk.java.net/display/JDKUpdates/JDK11u
[2]
https://qa.debian.org/developer.php?login=pkg-java-maintainers@lists.alioth.debian.org
Reply to: