Summary: | Request to keyword qemu-kvm-0.12.2 as stable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | justXi <gentoo> |
Component: | New packages | Assignee: | Gentoo QEMU Project <qemu+disabled> |
Status: | RESOLVED CANTFIX | ||
Severity: | enhancement | CC: | kfm |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.qemu.org | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
justXi
2010-01-20 09:30:00 UTC
+1 Fortunately, there's now an ebuild in the tree. It fixes at least one serious bug - that's bug 300049. Now one can only hope that the herd introduces a policy of reading their bugs ... we're stable requesting a package that has a half dozen bugs opened and was added to the tree within the last 8 hours? There must be a typo somewhere that I missed. I've already responded elsewhere. Suffice to say that I had intended to use this is a reference point for whittling down those bugs which are resolved by 0.12.2 and those which are not. Maybe I didn't do that in a way that follows the rule book but I submit that the premise itself is above patronisation. Frankly, if fixing bugs is is so important, I find it most curious that the relevant herds have shown no hestiation in committing new ebuilds which continue to propagate outstanding QA bugs for which bugs have *already* been filed. At least with newer upstream versions, us out there in pesky Userville benefit from the upstream bug fixes. Or are is there going to be a suddden spring to action and a concerted effort to backport these (serious) bug fixes? I doubt it very much. The original reporter's request was fulfilled. Considered formally, my request cannot be resolved and is just so much clutter in bugzilla; I duly retract it. |