[Pkg-xen-devel] Bug#640500: Bug#640500: Acknowledgement (xen-hypervisor-4.0-amd64: xend invokes oomkiller and reboots machine when creating DomU's)

[Thomas Goirand]

On 09/05/2011 07:33 PM, Wiebe Cazemier wrote:
> Severity is set to normal, but I set it to grave or serious in the bug
> report tool. This bug is more severe than 'normal', in any case.

Not discussing the bug itself, but just FYI...

Please read about the severity when reporting. "serious" is mostly
reserved for the Debian policy violation:

serious: is a severe violation of Debian policy (that is, the problem is
a violation of a 'must' or 'required' directive); may or may not affect
the usability of the package. Note that non-severe policy violations may
be 'normal,' 'minor,' or 'wishlist' bugs. (Package maintainers may also
designate other bugs as 'serious' and thus release-critical; however,
end users should not do so.)

In your case, it might deserves a severity "important" if you think that
"normal" doesn't fit:

important: a bug which has a major effect on the usability of a package,
without rendering it completely unusable to everyone.

vs

normal: a bug that does not undermine the usability of the whole
package; for example, a problem with a particular option or menu item.

The Xen hypervisor, in this case, is not "completely unusable to
everyone", so severity "important" might be the highest severity.

The other 2 higher seriousness would be:

1 critical: makes unrelated software on the system (or the whole system)
break, or causes serious data loss, or introduces a security hole on
systems where you install the package.

or

2 grave: makes the package in question unusable by most or all users, or
causes data loss, or introduces a security hole allowing access to the
accounts of users who use the package.

and none are your case, IMO. Please pay attention to the definitions of
seriousness next time you do a bug report.

Thomas Goirand (zigo)