[Pkg-libvirt-maintainers] Bug#675059: marked as done (libvirt-bin: libvirtd doesn't start on >65KiB long dmidecode output)

[Debian Bug Tracking System]

Your message dated Wed, 30 May 2012 08:08:28 +0200
with message-id <20120530060828.GB12972 at bogon.sigxcpu.org>
and subject line Re: [Pkg-libvirt-maintainers] Bug#675059: libvirt-bin: libvirtd doesn't start on >65KiB long dmidecode output
has caused the Debian Bug report #675059,
regarding libvirt-bin: libvirtd doesn't start on >65KiB long dmidecode output
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
675059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675059
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Vlastimil Holer <vlastimil.holer at gmail.com>
Subject: libvirt-bin: libvirtd doesn't start on >65KiB long dmidecode output
Date: Tue, 29 May 2012 17:21:31 +0200
Size: 88874
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20120530/a3495e7e/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Guido =?iso-8859-1?Q?G=FCnther?= <agx at sigxcpu.org>
Subject: Re: [Pkg-libvirt-maintainers] Bug#675059: libvirt-bin: libvirtd doesn't start on >65KiB long dmidecode output
Date: Wed, 30 May 2012 08:08:28 +0200
Size: 96567
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20120530/a3495e7e/attachment-0003.mht>