Furthermore I've built (again the very same source) in groovy as 5.2+dfsg-9ubuntu2~groovyppa1 in the same PPA.
This build works as well in my tries.
So I have the same code as in "1:5.2+dfsg-9ubuntu1" three times now:
1. [1] => built 2021-03-23 in Hirsute => works
2. [2] => built 2021-04-12 in Hirsute => fails
3. [3] => built 2021-04-13 in Groovy => works
With the two results above, I expected as next step could spin up a (git based)
Groovy and a Hirsute build environment.
I'd do a build from git (and optimize a bit for build speed).
If these builds confirm the above results of [2] and [3] then I should be able
to upgrade the components in the Groovy build environment one by one to Hirsute
To identify which one is causing the breakage...
But unfortunately I have to start to challenge the reproducibility and that is
breaking the camels back here. Without that I can't go on well, and as sad (it
is a real issue) as it is it is riscv64 emulation on an arm64 host really isn't
the most common use case. So I'm unsure how much time I can spend on this.
Maybe I have looked at this from the wrong angle, let me try something else before I give up ...
Furthermore I've built (again the very same source) in groovy as 5.2+dfsg- 9ubuntu2~ groovyppa1 in the same PPA.
This build works as well in my tries.
So I have the same code as in "1:5.2+ dfsg-9ubuntu1" three times now:
1. [1] => built 2021-03-23 in Hirsute => works
2. [2] => built 2021-04-12 in Hirsute => fails
3. [3] => built 2021-04-13 in Groovy => works
[1]: https:/ /launchpad. net/ubuntu/ +source/ qemu/1: 5.2+dfsg- 9ubuntu1/ +build/ 21196422 /launchpad. net/~paelzer/ +archive/ ubuntu/ lp-1921664- testbuilds- rebuildold/ +build/ 21392458 /launchpad. net/~paelzer/ +archive/ ubuntu/ lp-1921664- testbuilds- rebuildold/ +build/ 21394457
[2]: https:/
[3]: https:/
With the two results above, I expected as next step could spin up a (git based)
Groovy and a Hirsute build environment.
I'd do a build from git (and optimize a bit for build speed).
If these builds confirm the above results of [2] and [3] then I should be able
to upgrade the components in the Groovy build environment one by one to Hirsute
To identify which one is causing the breakage...
But unfortunately I have to start to challenge the reproducibility and that is
breaking the camels back here. Without that I can't go on well, and as sad (it
is a real issue) as it is it is riscv64 emulation on an arm64 host really isn't
the most common use case. So I'm unsure how much time I can spend on this.
Maybe I have looked at this from the wrong angle, let me try something else before I give up ...