-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aurelien Jarno wrote:
> severity 419929 important
> thanks
> 
> On Wed, Apr 18, 2007 at 10:08:33PM +0200, Johannes Wiedersich wrote:
>> Package: qemu
>> Version: 0.8.2-4
>> Severity: critical
>> Justification: causes serious data loss
> 
> This only concerns one feature of qemu, and only concerns the data you
> try to modify in the guest. It's data loss, but I won't call that
> *serious* data loss.

I won't be picky about what kind of data loss is serious or not. In this
particular case, user data are get corrupted without any user
interaction except opening and modifying a document. If you wouldn't
call that 'serious data loss' at least you should call it 'data loss'.
That means severity 'grave' [1], not important.

>> I use
>>
>> qemu win98bug.img -hdb fat:rw:test
>>
>> I know from /usr/share/doc/qemu/qemu-doc.html that I shouldn't use
>> non-ASCII filenames, etc.
>>
>> Apparently data loss occurs, if the *contents* of the file contain some
>> non-ASCII characters.
[snip]

> I really doubt it is due do non-ASCII characters. It's probably due to
> buffers not written to the disk when the guest is shutdown.
> 
> There has been a lot of code changes on that side in qemu 0.9.0, so I
> really think the bug has been fixed. Care to retry with this version ?

I would like to. The only problem is that I am quite happy at the moment
with my *stable* system(s) and updating would require to also update
libc6, essentially moving too much of the system to testing/unstable.

Are you planning on releasing a backport? It will require some time and
space for me to install and setup another system for verification of
this issue.

Thanks,

Johannes

[1] http://www.debian.org/Bugs/Developer#severities
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGf45MC1NzPRl9qEURAotpAJ0eTYZOUOkHt1ugDC57L1u+JtkO8ACeNO12
H/TOztmNYAADvQ9Qy/AIoWM=
=4mcm
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to