Bug#852324: Not a fatal error/warning

[Helio Loureiro <helio@loureiro.eng.br>]

Hi Didi,

I do know that was incorrect and I was wrong.  I filled up the info about my fix in my previous email.  But thanks for your reply.

Vänliga hälsningar/Best Regards,
Helio Loureiro
http://helio.loureiro.eng.br
https://se.linkedin.com/in/helioloureiro
http://twitter.com/helioloureiro

Note: if you failed to reach me, try my alternative mail "helio.loureiro@gmail.com".
I'm implementing DKIM on my mail server, so some disturbance is expected.

On Fri, Nov 2, 2018 at 5:05 AM Diederik de Haas <didi.debian@cknow.org> wrote:

On Wed, 26 Jul 2017 19:23:23 +0200 Helio Loureiro <helio@loureiro.eng.br>
wrote:
> He clearly states it isn't booting.  It is crashing.

No, that is an incorrect assessment.

I called it an error because I saw a stacktrace which I associate with an
error, even though the first line after "[ cut here ]" said warning.
But it wasn't a fatal error as Xen/linux completed the boot process, thus
severity 'normal'.
If it was fatal I'd set the severity to 'import' or 'grave' (against the xen
package as I then thought that was where the problem was).

So Ian's assessment/conclusion was correct.