I can confirm there are issues buiding on master, I was just looking into those myself.

I would suggest you group your changes in smaller commits, e.g. according to https://docs.yoctoproject.org/contributor-guide/submit-changes.html#implement-and-commit-changes

also look at your patch status, e.g Upstream-Status: Inappropriate [dead project] should probably be Upstream-Status: Inactive-Upstream [lastcommit: when (and/or) lastrelease: when]. See https://docs.yoctoproject.org/contributor-guide/recipe-style-guide.html#patch-upstream-status

also look at your patch status, e.g Upstream-Status: Inappropriate [dead project] should probably be Upstream-Status: Inactive-Upstream [lastcommit: when (and/or) lastrelease: when].

The thing is that some of the source codes were made in the late nineties. No source code can be considered original. It is impossible to determine who made the last reliable commit and when.

That's why I used the wording that the developer of this recipe had previously used for other patches.

I would suggest you group your changes in smaller commits

I split one commit into several, separating them by meaning.

Guys, is there anything else needed for acceptance? How about a merge?

the tl;dr would be have openjdk-8-test-image and openjre-8-test-image buildable for qemuarm, qemuarm64 and qemux86-64,

I'll refer you to https://lists.yoctoproject.org/g/yocto-patches/message/986 for the details

unfortunately I haven't had the time to look into that, which I wanted to do before this MR