04.07.2021 15:02, Rich wrote:
When I tried building qemu 6.0 or git on buster, as I recall it
errored out on dependencies not available in sufficiently new
incarnations, even in backports.
If the answer to "this is quite buggy" is "just run a version not even
in unstable yet", that's...quite unfortunate.
If you're just saying this because it's qemu upstream's opinion, well,
I knew that. :)
Hi Rich!
I'm sorry to disappoint you, but this was all I was able to offer.
It is not "qemu upstream's opinion", it is my opinion, - it fells
like riscv64 in 3.1 was quite buggy and there's nothing I can do
about it, - I definitely wont backport changes from 6.0 to buster's
3.1 version.
Usually qemu builds quite well on current distributions, including
debian buster. I backported 5.2 version (from bullseye) for buster
together with 2 or 3 new dependencies which were not in buster.
I can not, at the time, provide a more recent version of qemu
(6.0) even for unstable since - at the time - debian was frozen
before bullseye release. However, I did provide 6.0 version
in experimental - this is the only way I know to actually
provide a new upstream version for debian during freeze.
Ofcourse I can't provide backport of 6.0 for buster since it
wasn't in bullsyeye or instable.
So your disapproval of my answer stays solely with you - I did
everything I was able to do. And I definitely suggested you the
only realistic - to my opinion - way to go forward - which is to
try either latest stable version or even the current development
version. Because this is the only way to ensure if the bug you're
seeing is already fixed.
Meanwhile, 6.1 has been released (yesterday) and it is already
available on debian unstable today.
/mjt
