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

Bug#1036040: marked as done (unblock: qemu/1:7.2+dfsg-7)



Your message dated Mon, 15 May 2023 20:26:48 +0000
with message-id <E1pyemO-002duB-2y@respighi.debian.org>
and subject line unblock qemu
has caused the Debian Bug report #1036040,
regarding unblock: qemu/1:7.2+dfsg-7
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.)


-- 
1036040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036040
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: qemu@packages.debian.org, pkg-qemu-devel@lists.alioth.debian.org
Control: affects -1 + src:qemu

Please unblock package qemu
This is an easy one.

[ Reason ]
This release contains a fix for a trivial packaging bug, --
a forgotten Depends during package split. See the changelog
entry for more details.

[ Risks ]
There's no risks. The fix just works (tm).

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

(even in such a trivial case, I managed to forget to format the Closes:
line properly, This does not affect the package thogh)

unblock qemu/1:7.2+dfsg-7

diff -Nru qemu-7.2+dfsg/debian/changelog qemu-7.2+dfsg/debian/changelog
--- qemu-7.2+dfsg/debian/changelog	2023-04-29 13:02:55.000000000 +0300
+++ qemu-7.2+dfsg/debian/changelog	2023-05-14 11:29:12.000000000 +0300
@@ -1,3 +1,24 @@
+qemu (1:7.2+dfsg-7) unstable; urgency=medium
+
+  * d/control: qemu-system-xen: add ipxe-qemu dependency (#1035676)
+
+    When installing qemu-system-xen on a new system, the boot roms are
+    not installed. Unfortunately this means HVM Xen DomUs can not be used
+    at all, because the boot roms are hard requiriment for qemu since 2014,
+    it fails to start without the boot roms even if (network) booting is
+    not requested.
+
+    Before bookworm, when qemu-system-xen was part of regular
+    qemu-system-x86 package, the dependency on ipxe-qemu was coming from
+    that package. But when splitting qemu-system-xen out of it, we forgot
+    that the boot roms are hard dependency now. This makes qemu-system-xen
+    unusable on a new install until ipxe-qemu is installed too.
+
+    An alternative would be to revert upstream commit 178e785fb
+    (from 2014) to make rom loading failure a non-fatal error.
+
+ -- Michael Tokarev <mjt@tls.msk.ru>  Sun, 14 May 2023 11:29:12 +0300
+
 qemu (1:7.2+dfsg-6) unstable; urgency=medium
 
   [ Michael Tokarev ]
diff -Nru qemu-7.2+dfsg/debian/control qemu-7.2+dfsg/debian/control
--- qemu-7.2+dfsg/debian/control	2023-04-29 12:31:07.000000000 +0300
+++ qemu-7.2+dfsg/debian/control	2023-05-11 17:28:22.000000000 +0300
@@ -400,7 +400,7 @@
 Multi-Arch: no
 # do we really need qemu-system-data? keymaps only?
 Depends: ${shlibs:Depends}, ${misc:Depends}, qemu-system-data (>> ${source:Upstream-Version}~),
- seabios
+ seabios, ipxe-qemu
 Recommends: qemu-utils,
  ovmf,
 Description: QEMU full system emulation (Xen helper package)
diff -Nru qemu-7.2+dfsg/debian/control-in qemu-7.2+dfsg/debian/control-in
--- qemu-7.2+dfsg/debian/control-in	2023-04-29 12:05:13.000000000 +0300
+++ qemu-7.2+dfsg/debian/control-in	2023-05-07 21:55:26.000000000 +0300
@@ -412,7 +412,7 @@
 Multi-Arch: no
 # do we really need qemu-system-data? keymaps only?
 Depends: ${shlibs:Depends}, ${misc:Depends}, qemu-system-data (>> ${source:Upstream-Version}~),
- seabios
+ seabios, ipxe-qemu
 Recommends: qemu-utils,
  ovmf,
 :ubuntu:# For the transition from the former qemu-system-x86-xen name

--- End Message ---
--- Begin Message ---
Unblocked.

--- End Message ---

Reply to: