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

Accepted qemu 1:8.0.2+dfsg-2 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 15 Jun 2023 22:25:50 +0300
Source: qemu
Architecture: source
Version: 1:8.0.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team <pkg-qemu-devel@lists.alioth.debian.org>
Changed-By: Michael Tokarev <mjt@tls.msk.ru>
Closes: 1037341
Changes:
 qemu (1:8.0.2+dfsg-2) unstable; urgency=medium
 .
   * d/rules: --enable-libusb for xen build (Closes: #1037341)
   * reapply linux-user-binfmt-P.diff.
     Re-rely on qemu-user's argv0 to detect it is running in binfmt context.
     The problem is that while we ship kernel which can pass this info the
     qemu way, there are many containers which are running on older kernels
     still, including bullseye kernel (5.10) which does not have this feature.
     Keep it for a bit more.
   * hw_intc_allwinner-a10-pic-handle-IRQ-levels-other-than-0-or-1.patch
     Pick a patch from upstream mailinglist to fix regression in 8.0.2
Checksums-Sha1:
 960b0652e1a9a82265736eb6333b67e7660e0f8a 7595 qemu_8.0.2+dfsg-2.dsc
 23af48454f2cc8a36a3a442b4513e7d3602eb055 106180 qemu_8.0.2+dfsg-2.debian.tar.xz
 193d4dcce0e77a04dc7122d5defdc3921f14406f 13868 qemu_8.0.2+dfsg-2_source.buildinfo
Checksums-Sha256:
 dea489d7c86a71e300b73fb51a043a1cf0c098bc249f0312cf663a2c5a1a8bc9 7595 qemu_8.0.2+dfsg-2.dsc
 59ed72305872d25b620d88c927e271132a35ac96957448318819f46bee194a02 106180 qemu_8.0.2+dfsg-2.debian.tar.xz
 698d2b855e91016cec06255fb08bf1c9d6e71b356a09d7e90d31a08f0e8bff84 13868 qemu_8.0.2+dfsg-2_source.buildinfo
Files:
 5432996f984bd061bf393fad6a85b3af 7595 otherosfs optional qemu_8.0.2+dfsg-2.dsc
 9a0293582deb40ac9548a6f7f298325e 106180 otherosfs optional qemu_8.0.2+dfsg-2.debian.tar.xz
 f40100a3055bd4b82a54acfaf5eaf069 13868 otherosfs optional qemu_8.0.2+dfsg-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQFDBAEBCgAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAmSLZ6YPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5Z2zkH+wdrzqfaBaTTvyDN/PzcGteJCtbBIQisZjDh
gDLdmAXQbFeQee5GkWJD/qE6IHZmw3DaSTBFcRTbYZKNMwaES0GFUj3ZZZNk4s4F
RDrZjtuiZDhClb7V9wnEmm0o1nt+hw6w5GyJEsDNErdC+3d1Xumy6dGfajoqVPC1
SdX+lgxPX/dWPpNrsCktiHW97sUmsjBaXsA5NTlcnAMz37FXGiRBR1usENY61doQ
uy+dM8jeW/rD6wDd/7aBctBzwWacOF1d76l/hDw2+Og1BYtdiHQSrN8xh64tj7ho
5mlMfTYleB3sqjZQWyDxcLrwBUCUPmGry7r3pSnPEmAMQAVwnnw=
=ATyx
-----END PGP SIGNATURE-----


Reply to: