Bug#1115486: trixie-pu: package qemu/1:10.0.4+ds-0+deb13u1

[Michael Tokarev <mjt@tls.msk.ru>]

On 10/19/25 18:56, Jonathan Wiltshire wrote:
> Control: tag -1 confirmed
>
> Hi,
>
> Please go ahead.

Heh.  Thanks.  You're just in time ;)

The thing is: there's a migration regression in qemu release 10.0.4,
it lasted up to 10.0.5 (current upstream stable), and we corrected
it for 10.0.6 which is planned to be released tomorrow (after which
I'll go for the trixie-pu for sure).

So I'm not sure what to do now - to upload the "wrong" 10.0.4 to
trixie-pu, and make another pu tomorrow on top of it, or skip the
upload of 10.0.4, and - update this bug report for 10.0.6?

The prob with 10.0.4 is that there were two bugfixes in that release,
which happen to break migration from older releases (including
previous 10.0.x).  Unfortunately there's no way around this, - it is
either the migration which is broken, or the two bugs remains.  We
(upstream qemu) decided we never broke migration this way before, so
we reverted the two fixes for the upcoming 10.0.6.  Which is unfortunate
but here we go.

Thankfully, so far, it hasn't been a prob in debian, since 10.0.4 and
10.0.5 hasn't been in trixie-pu so far.

So.  I think I'll file a new bug report for the new upcoming version,
but refrain from uploading the confirmed 10.0.4 until 10.0.6 is
confirmed?  What do you think?

Thanks,

/mjt