23.07.2020 18:18, eighty-...@leadingpeak.ca wrote: > Thanks for fixing this so promptly. > > I assumed it would take some time to propagate the fix, but it's been > 24 > hours. The 1:5.0-11 package is still not available in Buster.
I uploaded the fixed 3.1+dfsg-8+deb10u7 version to buster-security at Wed Jul 22 14:02:48 2020 +0300, which is 29 hours ago, and which was before this bug has been reopened, too. It should be available in the archives once the infrastructure catches up, we had another issue to solve with other bug elsewhere prevented this version to compile. > I also want to note that it wasn't me that reopened the bug and bumped up the > severity level. I agree with your reply to the effect that this is not > end-of-the-world stuff. You just received my reply as the original reporter of this bug. It wasn't targetted at you really. I'm sorry about that. > At the same time, I'd give you and argument over the seriousness level - I > still think it's important. Xen domUs won't start. Xen is a very widely It *is* important, I agreed. It definitely is not critical, it does not break other software in any way, it does not do its function. Yes this affects other software, just like many many other cases - e.g. a bug in glibc might affect many other programs, but this does not mean it *breaks* other programs, it is just a bug in certain use case of glibc. It is very important nevertheless to fix it as soon as possible, and I used all my energy to fix this very issue in qemu as soon as I can, - it isn't always a 5-minute job to identify the problem and find a solution to it. I done my part, now we're all waiting for the updated version to show up. ... > I don't care either way though so long as 1:5.0-11 is available soon. 5.0-11 wont be in buster, buster has version 3.1. Thanks, /mjt
