jdk8u322 release and packaging

[Severin Gehwolf]

Hi,

On Sat, 2022-01-22 at 22:07 +0100, Thorsten Glaser wrote:
> Hi,
> 
> I’m currently packaging openjdk-8 for Debian (unstable, where
> it is tested for LTS/ELTS updating older releases). I have
> taken it over from the previous maintainer, but I am “mostly”
> keeping this alive.
> 
> I see that the 8u322 release (which I had put into my calendar
> https://wiki.openjdk.java.net/display/jdk8u/Main#Main-Timelines
> from ↑) seems to be delayed because of repository changes.
> 
> These repository changes are a problem. The packaging depends
> heavily on being able to download the individual hg releases’
> tarballs, plus aarch32 and aarch64-shenandoah, separately and
> put them together in suitable ways depending on the architecture
> building for.
> 
> As I said above, I’ve taken this over because nobody else was
> doing it so I’m not heavily invested in this packaging. I’m
> trying to not change too much.
> 
> Is there any way (which will stay stable, even when you’re going
> to move repositories *again*, to git) to split the download into
> what the old repositories have been, so I can still get my tarballs
> in the way the current packaging requires?

The currently actively maintained tree is the jdk8u-monorepo[1] tree.
There is a *live* git mirror of it here:
https://github.com/openjdk/jdk8u

For packaging purposes the git mirror can be used. It'll stay. Once we
switch from HG to git the mirror becomes the main tree and the HG repo
gets switched to read-only mode.

I believe the same is true for aarch32[2] and shenandoah trees[3].

HTH,
Severin

[1] https://hg.openjdk.java.net/jdk8u/monojdk8u
[2] https://github.com/openjdk/aarch32-port-jdk8u
[3] https://bugs.openjdk.java.net/browse/SKARA-1290
    i.e. https://github.com/openjdk/shenandoah-jdk8u


> Otherwise I’d have to change things a lot, which will be tricky
> *and* time-consuming (and I’d have to ask $employer for more time
> than I can currently use for this).
> 
> I’d prefer best if you would just push the new releases also to
> the old repositories and tag them appropriately. But I understand
> chances for this going to happen are small as you seem to be very
> interested in this new-fangled git thingy :/
> 
> Thanks in advance,
> //mirabilos