[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1100970: marked as done (pre-approval: qemu 10.0 for trixie)

Your message dated Thu, 8 May 2025 10:27:22 +0300
with message-id <7955e4c0-41b7-4718-97a2-6fcb50751f79@tls.msk.ru>
and subject line Re: Bug#1100970: pre-approval: qemu 10.0 for trixie
has caused the Debian Bug report #1100970,
regarding pre-approval: qemu 10.0 for trixie
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@bugs.debian.org
immediately.)


-- 
1100970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100970
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: pkg-qemu-devel@lists.alioth.debian.org

Hi!

I would like to include upstream qemu version 10.0 in trixie.
Currently, qemu is at release-candidate stage, 10.0.0-rc0, and
the actual release is planned for 2025-04-15 (or 2025-04-22 if
a critical bug is found during the release process) -- the same
day as the planned freeze of trixie.  The upstream release
schedule is at https://wiki.qemu.org/Planning/10.0 .

Currrently, qemu 10.0.0-rc0 is uploaded to debian experimental,
and it works quite well so far.  Obviously it is possible to
discover bugs after the uplstream release too, - this is dealt
in the upstream stable/bugfix releases, with usual schedule
about every month.

The reason why I'd love to have 10.0 in trixie (instead of current
9.2) is the need to support qemu during the trixie life cycle,
which means back-porting fixes.  Qemu is a fast-moving target
still, and it is increasingly difficult to support older releases
for long time.  I plan to provide a long-term upstream series for
the qemu version we will ship in debian trixie.

Qemu is critical for debian infrastructure, this is why I'd love
to have as strong support background for it as possible.

At the same time, possible issues in qemu which are found during
trixie freeze might require extra efforts from everyone, including
me as qemu maintainer, and the release team.  So there's a risk
here.  On the other hand, qemu from trixie is not used to build
trixie currently, so the risk shouldn't be that much.

I plan to upload 10.0.0-rc0 to sid tomorrow, once debci tests
for the current version in experimental are completed.

Thanks,

/mjt

--- End Message ---
--- Begin Message --- 
The requested version has been migrated to testing with (almost)
no manual intervention, and this bug can now be closed.  For some
reason I thought 10.0 wont make it into trixie without manual
action.

Thanks,

/mjt

--- End Message ---
Reply to: