From owner at bugs.debian.org Sun Jun 1 00:39:01 2025 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 31 May 2025 23:39:01 +0000 Subject: [Pkg-libvirt-maintainers] Processed: Re: Bug#1104735: libvirt: cannot restore internal snapshots References: <3328680.jZfb76A358@tuxin> <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> Message-ID: Processing control commands: > tag -1 + patch Bug #1104735 [src:libvirt] libvirt: cannot restore internal snapshots Added tag(s) patch. -- 1104735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104735 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From hefee at debian.org Sun Jun 1 00:37:04 2025 From: hefee at debian.org (Hefee) Date: Sun, 01 Jun 2025 01:37:04 +0200 Subject: [Pkg-libvirt-maintainers] Bug#1104735: libvirt: cannot restore internal snapshots In-Reply-To: <874ixorgwq.fsf@manticora> References: <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> Message-ID: <3328680.jZfb76A358@tuxin> Control: tag -1 + patch Hi, Upstream fixed the issue with a bigger merge request. We tested the miinimal fix for it and the only needed fix is : https://gitlab.com/libvirt/libvirt/-/commit/ 889d2ae289cd95d612575ebc7a4e111ac33b0939 I created a mr on salsa, will you do the paperwork for the freeze exception? Or should I do a NMU? the merge request: https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/266 Regards, hefee -- On Tue, 13 May 2025 11:36:37 +0200 intrigeri wrote: > Control: forwarded -1 https://gitlab.com/libvirt/libvirt/-/issues/771 > Control: tag -1 + upstream > > Hi, > > anonym forwarded this upstream, who already reproduced, confirmed it's > a regression, and bisected. Fingers crossed that a fix can be > implemented upstream soon and that we can get it in Trixie, > with a freeze exception if necessary :) > > Cheers > -- > intrigeri > > -- Mein ?ffentlicher Schl?ssel / My public key: 0x19221BC085BE851F Fingerabdruck / Fingerprint: EF09 31C4 ACED 4606 C314 0E7C 1922 1BC0 85BE 851F runterladen/download: https://keys.openpgp.org/vks/v1/by-fingerprint/ EF0931C4ACED4606C3140E7C19221BC085BE851F -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: From eof at kiyuko.org Sun Jun 1 15:57:55 2025 From: eof at kiyuko.org (Andrea Bolognani) Date: Sun, 1 Jun 2025 16:57:55 +0200 Subject: [Pkg-libvirt-maintainers] Bug#1104735: Bug#1104735: libvirt: cannot restore internal snapshots In-Reply-To: <3328680.jZfb76A358@tuxin> References: <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> <3328680.jZfb76A358@tuxin> <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> Message-ID: <20250601145755.vtbrevf3rikxmp7c@meyneth> On Sun, Jun 01, 2025 at 01:37:04AM +0200, Hefee wrote: > Control: tag -1 + patch > > Hi, > > Upstream fixed the issue with a bigger merge request. We tested the miinimal fix > for it and the only needed fix is : > https://gitlab.com/libvirt/libvirt/-/commit/ > 889d2ae289cd95d612575ebc7a4e111ac33b0939 > > I created a mr on salsa, will you do the paperwork for the freeze exception? > Or should I do a NMU? > > the merge request: > > https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/266 Hi, I was planning to handle this over the next few days. Thanks for the reminder. I have prepared an alternate MR: https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/267 This are handled slightly differently compared to what you had in order to comply with the established conventions for the libvirt package. I will take care of the paperwork. Cheers. -- Andrea Bolognani Resistance is futile, you will be garbage collected. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From hefee at debian.org Sun Jun 1 17:01:04 2025 From: hefee at debian.org (Hefee) Date: Sun, 01 Jun 2025 18:01:04 +0200 Subject: [Pkg-libvirt-maintainers] Bug#1104735: Bug#1104735: libvirt: cannot restore internal snapshots In-Reply-To: <20250601145755.vtbrevf3rikxmp7c@meyneth> References: <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> <3328680.jZfb76A358@tuxin> <20250601145755.vtbrevf3rikxmp7c@meyneth> <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> Message-ID: <3746064.yKrmzQ4Hd0@tuxin> Hi, > I was planning to handle this over the next few days. Thanks for the > reminder. > > I will take care of the paperwork. Thanks a lot for taking over and do the paperwork! Regards, hefee -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: From eof at kiyuko.org Sun Jun 1 16:56:43 2025 From: eof at kiyuko.org (Andrea Bolognani) Date: Sun, 1 Jun 2025 17:56:43 +0200 Subject: [Pkg-libvirt-maintainers] Bug#1107107: unblock: libvirt/11.3.0-2 Message-ID: <20250601155643.7uqwwg6v2rtponj4@meyneth> Package: release.debian.org Severity: normal User: release.debian.org at packages.debian.org Usertags: unblock X-Debbugs-Cc: libvirt at packages.debian.org Control: affects -1 + src:libvirt Please unblock package libvirt. [ Reason ] Apply fix for #1104735. [ Tests ] The backport has been confirmed to address the issue in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104735#25 [ Risks ] Very little risk of causing regressions. The fix is small and targeted, and it comes directly from upstream with no changes. [ 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 unblock libvirt/11.3.0-2 -- Andrea Bolognani Resistance is futile, you will be garbage collected. -------------- next part -------------- diff -Nru libvirt-11.3.0/debian/changelog libvirt-11.3.0/debian/changelog --- libvirt-11.3.0/debian/changelog 2025-05-02 20:25:28.000000000 +0000 +++ libvirt-11.3.0/debian/changelog 2025-06-01 14:39:44.000000000 +0000 @@ -1,3 +1,11 @@ +libvirt (11.3.0-2) unstable; urgency=medium + + * [eb4a97a] patches: Add backports + - backport/[...]-Don-t-setup-qemu-for-inco.patch + - Closes: #1104735 + + -- Andrea Bolognani Sun, 01 Jun 2025 16:39:44 +0200 + libvirt (11.3.0-1) unstable; urgency=medium * [228f666] New upstream version 11.3.0 diff -Nru libvirt-11.3.0/debian/patches/backport/qemuProcessStartWithMemoryState-Don-t-setup-qemu-for-inco.patch libvirt-11.3.0/debian/patches/backport/qemuProcessStartWithMemoryState-Don-t-setup-qemu-for-inco.patch --- libvirt-11.3.0/debian/patches/backport/qemuProcessStartWithMemoryState-Don-t-setup-qemu-for-inco.patch 1970-01-01 00:00:00.000000000 +0000 +++ libvirt-11.3.0/debian/patches/backport/qemuProcessStartWithMemoryState-Don-t-setup-qemu-for-inco.patch 2025-06-01 14:39:44.000000000 +0000 @@ -0,0 +1,62 @@ +From: Peter Krempa +Date: Tue, 13 May 2025 19:07:20 +0200 +Subject: qemuProcessStartWithMemoryState: Don't setup qemu for incoming + migration when reverting internal snapshot + +The memory/device state of the VM for an internal snapshot is restored +by qemu itself via a QMP command and is taken from the qcow2 image, thus +we don't actually do any form of incoming migration. + +Commit 5b324c0a739fe00 which refactored the setup of the incoming +migration state didn't take the above into account and inadvertently +caused that qemu is being started with '-incoming defer' also when +libvirt would want to revert an internal snapshot. + +Now when qemu expects incoming migration it doesn't activate the block +backends as that would cause locking problems and image inconsistency, +but also doesn't allow the use of the images. Since the block backends +are not activated qemu then thinks that they don't actually support +internal snapshots and reports: + + error: operation failed: load of internal snapshot 'foo1' job failed: Device 'libvirt-1-format' is writable but does not support snapshots + +Due to the above bug it's not possible to revert to internal snapshots +in libvirt-11.2 and libvirt-11.3. + +Fixes: 5b324c0a739fe00cbec209219db4488742492112 +Resolves: https://issues.redhat.com/browse/RHEL-88747 +Closes: https://gitlab.com/libvirt/libvirt/-/issues/771 +Signed-off-by: Peter Krempa +Reviewed-by: Jim Fehlig +Reviewed-by: Michal Privoznik +(cherry picked from commit 889d2ae289cd95d612575ebc7a4e111ac33b0939) + +Bug-Debian: https://bugs.debian.org/1104735 + +Forwarded: not-needed +Origin: https://gitlab.com/libvirt/libvirt/-/commits/889d2ae289cd95d612575ebc7a4e111ac33b0939 +--- + src/qemu/qemu_process.c | 10 +++++++--- + 1 file changed, 7 insertions(+), 3 deletions(-) + +diff --git a/src/qemu/qemu_process.c b/src/qemu/qemu_process.c +index 1af91c5..5f2203d 100644 +--- a/src/qemu/qemu_process.c ++++ b/src/qemu/qemu_process.c +@@ -8636,9 +8636,13 @@ qemuProcessStartWithMemoryState(virConnectPtr conn, + /* The fd passed to qemuProcessIncomingDefNew is used to create the migration + * URI, so it must be called after starting the decompression program. + */ +- incoming = qemuProcessIncomingDefNew(driver, vm, NULL, "stdio", fd, path, data, migParams); +- if (!incoming) +- return -1; ++ if (!snapshot) { ++ /* Internal snapshots are reverted by a QMP command after qemu is started, ++ * so we don't actually want to setup incoming migration. */ ++ if (!(incoming = qemuProcessIncomingDefNew(driver, vm, NULL, "stdio", ++ fd, path, data, migParams))) ++ return -1; ++ } + + /* No cookie means libvirt which saved the domain was too old to mess up + * the CPU definitions. diff -Nru libvirt-11.3.0/debian/patches/series libvirt-11.3.0/debian/patches/series --- libvirt-11.3.0/debian/patches/series 2025-05-02 20:25:28.000000000 +0000 +++ libvirt-11.3.0/debian/patches/series 2025-06-01 14:39:44.000000000 +0000 @@ -1,3 +1,4 @@ +backport/qemuProcessStartWithMemoryState-Don-t-setup-qemu-for-inco.patch debian/Debianize-libvirt-guests.patch debian/apparmor_profiles_local_include.patch debian/Use-sensible-editor-by-default.patch -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From eof at kiyuko.org Sun Jun 1 17:12:55 2025 From: eof at kiyuko.org (Andrea Bolognani) Date: Sun, 1 Jun 2025 18:12:55 +0200 Subject: [Pkg-libvirt-maintainers] Bug#1104735: Bug#1104735: libvirt: cannot restore internal snapshots In-Reply-To: <3746064.yKrmzQ4Hd0@tuxin> References: <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> <3328680.jZfb76A358@tuxin> <20250601145755.vtbrevf3rikxmp7c@meyneth> <3746064.yKrmzQ4Hd0@tuxin> <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> Message-ID: <20250601161255.cst3bxyh5qcqrvfg@meyneth> On Sun, Jun 01, 2025 at 06:01:04PM +0200, Hefee wrote: > Hi, > > > I was planning to handle this over the next few days. Thanks for the > > reminder. > > > > I will take care of the paperwork. > > Thanks a lot for taking over and do the paperwork! Unblock request filed. https://bugs.debian.org/1107107 -- Andrea Bolognani Resistance is futile, you will be garbage collected. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From eof at kiyuko.org Sun Jun 1 21:04:55 2025 From: eof at kiyuko.org (Andrea Bolognani) Date: Sun, 1 Jun 2025 22:04:55 +0200 Subject: [Pkg-libvirt-maintainers] Bug#1104431: Bug#1104431: libvirt-daemon-driver-lxc: Starting libvirt_lxc container with MTU set to != 1500 doesn't set specified MTU on veth devices In-Reply-To: <174596507328.171823.7657335425346335176.reportbug@vmserver.garyhawkins.uk> References: <174596507328.171823.7657335425346335176.reportbug@vmserver.garyhawkins.uk> <174596507328.171823.7657335425346335176.reportbug@vmserver.garyhawkins.uk> Message-ID: <20250601200455.hxqozpjk7y2lxvpz@meyneth> On Tue, Apr 29, 2025 at 11:17:53PM +0100, Gary Hawkins wrote: > When I start an LXC container using virsh -c lxc:///system start > where the domain XML file for that container contains > something along the lines of: > > > > > > > > > > > > > > the container starts as expected, but the "vnet" veth device(s) > created as a result are always set to exactly 1500 MTU regardless > of what is specified for MTU in the domain XML. This only happens > when using LXC containers with libvirt; qemu/KVM VMs started with > libvirt set the MTU correctly. I am unsure whether this is a bug > in libvirt or whether the underlying systemd-container process is > handling this incorrectly. While it is possible to alter the MTU > of the veth device once started and make it work, that's not a > workable solution in the long term. > > What I expect to happen is that either the MTU is set on the veth > device as specified in the domain XML, or the XML does not allow > MTU to be set, but I cannot see anything in the libvirt > documentation to suggest that setting MTU is not a valid option > here. > > https://libvirt.org/formatdomain.html#mtu-configuration does not > seem to specify that is unacceptable for LXC > containers, so I assume this was meant to work. > > This is reproducible in the current 11.2.0-2 in trixie and also > 11.2.0-3 in experimental. (I have downgraded back to 11.0.2-2 now) To clarify, this doesn't work with 11.0.2-2 either, right? So it's not a regression in trixie compared to bookworm. Based on a quick look at the code, it seems that the necessary functionality has only been wired up in the QEMU and Cloud Hypervisor driver. Someone would have to modify the LXC driver to reach feature parity. I recommend that you file an upstream feature requrest here: https://gitlab.com/libvirt/libvirt/-/issues Once you've done so, we can mark this bug as "forwarded". -- Andrea Bolognani Resistance is futile, you will be garbage collected. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From owner at bugs.debian.org Mon Jun 2 22:07:02 2025 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 02 Jun 2025 21:07:02 +0000 Subject: [Pkg-libvirt-maintainers] Processed: Bug#1104735 marked as pending in libvirt References: <683e12292b659_3f010409657e@godard.mail> <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> Message-ID: Processing control commands: > tag -1 pending Bug #1104735 [src:libvirt] libvirt: cannot restore internal snapshots Added tag(s) pending. -- 1104735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104735 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From ftpmaster at ftp-master.debian.org Mon Jun 2 22:37:17 2025 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Mon, 02 Jun 2025 21:37:17 +0000 Subject: [Pkg-libvirt-maintainers] Processing of libvirt_11.3.0-2_source.changes Message-ID: libvirt_11.3.0-2_source.changes uploaded successfully to localhost along with the files: libvirt_11.3.0-2.dsc libvirt_11.3.0-2.debian.tar.xz libvirt_11.3.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) From ftpmaster at ftp-master.debian.org Mon Jun 2 22:51:56 2025 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Mon, 02 Jun 2025 21:51:56 +0000 Subject: [Pkg-libvirt-maintainers] libvirt_11.3.0-2_source.changes ACCEPTED into unstable Message-ID: Thank you for your contribution to Debian. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 01 Jun 2025 16:39:44 +0200 Source: libvirt Architecture: source Version: 11.3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Libvirt Maintainers Changed-By: Andrea Bolognani Closes: 1104735 Changes: libvirt (11.3.0-2) unstable; urgency=medium . * [eb4a97a] patches: Add backports - backport/[...]-Don-t-setup-qemu-for-inco.patch - Closes: #1104735 Checksums-Sha1: 302f4fa2390b752672236518b5db9e8aa706c9c0 7768 libvirt_11.3.0-2.dsc f1bdb20fe5b1452d4e60ca60cab97c993766274c 96608 libvirt_11.3.0-2.debian.tar.xz b351ded93c4f27080ba046bf76b00df5d0f8534a 13276 libvirt_11.3.0-2_source.buildinfo Checksums-Sha256: abe3bbeace4bb411792083bbb1e9cb54166a50366a03f07183e1978ebda3fdfb 7768 libvirt_11.3.0-2.dsc 3c70a85b00114a931301b6ca0eaf837ecd93b09bb813df04042a9454860fdb67 96608 libvirt_11.3.0-2.debian.tar.xz 859a86af07e438daa85aabc603eac182aecdda4510e936147ae81b613ed67753 13276 libvirt_11.3.0-2_source.buildinfo Files: 5c395d95abbc9ed8de63636202762bb3 7768 libs optional libvirt_11.3.0-2.dsc e01a591501d0b1d231df95273442f33b 96608 libs optional libvirt_11.3.0-2.debian.tar.xz 693802690e70e33bccd6a28463bcb4e0 13276 libs optional libvirt_11.3.0-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJDBAEBCgAtFiEEO48t9niVypx3EjLf954fxUKFg6wFAmg+Fp8PHGVvZkBraXl1 a28ub3JnAAoJEPeeH8VChYOsgZgP/07aJkrCS0fzRIiEWRsqdP70xNcb0e8BAoRw 3oykE16hUmBUXu7OxW/OWaaHGVLcGJbq9Pg9TOsDFeiWq3Iz3eMC6b4p7GN5LWP3 qITR+//Mazi+yRUpvESvMzvaxbjPGthc8BrBH7rs9cECvRscBabOXS6Qs7bR6fUi 6pwPKGC4exvhddBtSbuqysybjRvDxeRAS8pgAjRf3++QZ/fs7wuXKeEGlHOH8swu 9eUPG0zJ9umhs/EQdDCehoR/CUEufFNPYzpJtmYf+XldsaHb+sIuDiGpjQX4AtY6 uvZSSB9j2tsFmwwjj2HrBOSUpWswwucR6OeNWCrNDMHfdw0UPbPc7ukj2Bczzk6F bP4ud+LO9v/dPsKSlhohw0FhNKhuHjs0J0y12TxdWi5Uf++va65hiZfvO2kVSo1U KaZlgwbQguxWqGjl9SJasV78/BQZPboJoXNCJeCaLRVAtauDoz+bM0pFDfiDbp9m 69AS4rUyjn2oY8wyxEoVtjB9Ldvmi5DwYFPDjudl1nMeEgnny3bn5nWTwo0ulufH AH2f0sv6MHJ7QwZ0TrM+cguCWkBb9gBAAQ4U/GMkZhMWXZxVwMLLcFOPb5EbsMr1 gdJvGHoqidNBKWlseiWVCulJ2CwwEvkmTfxmoiWDHj1EMPFIflrmijC/jdIads6y Wmo3wXwI =uO1e -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available URL: From owner at bugs.debian.org Mon Jun 2 22:53:02 2025 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 02 Jun 2025 21:53:02 +0000 Subject: [Pkg-libvirt-maintainers] Bug#1104735: marked as done (libvirt: cannot restore internal snapshots) References: <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> Message-ID: Your message dated Mon, 02 Jun 2025 21:51:56 +0000 with message-id and subject line Bug#1104735: fixed in libvirt 11.3.0-2 has caused the Debian Bug report #1104735, regarding libvirt: cannot restore internal snapshots 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 at bugs.debian.org immediately.) -- 1104735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104735 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: anonym Subject: libvirt: cannot restore internal snapshots Date: Mon, 5 May 2025 14:43:55 +0200 Size: 6992 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#1104735: fixed in libvirt 11.3.0-2 Date: Mon, 02 Jun 2025 21:51:56 +0000 Size: 6863 URL: From steve at einval.com Tue Jun 3 00:48:37 2025 From: steve at einval.com (Steve McIntyre) Date: Tue, 3 Jun 2025 00:48:37 +0100 Subject: [Pkg-libvirt-maintainers] Bug#1106298: gnome-boxes: Debian netinst for "Debian 12 x86_64" points to missing debian-12.9.0-amd64-netinst.iso In-Reply-To: References: <174793591651.1869562.6028605476319334528.reportbug@cyclope.prahal.homelinux.net> <174793591651.1869562.6028605476319334528.reportbug@cyclope.prahal.homelinux.net> Message-ID: <20250602234837.GW7703@tack.einval.com> Hey Simon, On Thu, May 22, 2025 at 07:32:08PM +0100, Simon McVittie wrote: >Control: reassign -1 osinfo-db >Control: affects -1 + gnome-boxes > >On Thu, 22 May 2025 at 19:45:16 +0200, Alban Browaeys wrote: >> When choosing "Debian 12 x86_64" [in gnome-boxes] >> in create "Download an OS" (the plus dropdown) I get this error: >> ?chec du t?l?chargement de "debian-12.9.0-amd64-netinst.iso" : Not >> Found" >> ie likely "Failure to download ... debian-12.9.0-amd64-netinst.iso : Not Found" >> >> After a short search, I did not find the file where this iso location is defined. > >Looks like this comes from osinfo-db: >https://codesearch.debian.net/search?q=debian-12.9.0-amd64-netinst.iso&literal=1 >Does this need to be updated for every point release? > >debian-cd: is there a URL that this could point to without needing to specify >a concrete version number? This is for machine consumption (gnome-boxes is a >virtualization frontend) so it needs to be a direct link to the .iso, not a >web page with human-readable text, but HTTP redirects would probably be OK. > >https://cdimage.debian.org/cdimage/release/current/amd64/iso-cd/ looked >promising, but then the .iso filename still has the version number in it. I'll see what we can do... -- Steve McIntyre, Cambridge, UK. steve at einval.com The two hard things in computing: * naming things * cache invalidation * off-by-one errors -- Stig Sandbeck Mathisen From eof at kiyuko.org Tue Jun 3 19:31:59 2025 From: eof at kiyuko.org (Andrea Bolognani) Date: Tue, 3 Jun 2025 20:31:59 +0200 Subject: [Pkg-libvirt-maintainers] Bug#1104735: Bug#1104735: libvirt: cannot restore internal snapshots In-Reply-To: <20250601161255.cst3bxyh5qcqrvfg@meyneth> References: <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> <3328680.jZfb76A358@tuxin> <20250601145755.vtbrevf3rikxmp7c@meyneth> <3746064.yKrmzQ4Hd0@tuxin> <20250601161255.cst3bxyh5qcqrvfg@meyneth> <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> Message-ID: <20250603183159.ncusv2okjrf7r2hf@meyneth> On Sun, Jun 01, 2025 at 06:12:55PM +0200, Andrea Bolognani wrote: > Unblock request filed. Hefee, in the unblock bug I got the following request[1]: > Please go ahead with the upload and remove the moreinfo tag from > this unblock request once the new upload has been in unstable for a > few days, and has been confirmed to fix the issue. When you get a chance this week, can you please confirm that the package that was uploaded to unstable fixes that issue for you? Thanks. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107107#12 -- Andrea Bolognani Resistance is futile, you will be garbage collected. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From hefee at debian.org Tue Jun 3 20:36:36 2025 From: hefee at debian.org (Hefee) Date: Tue, 03 Jun 2025 21:36:36 +0200 Subject: [Pkg-libvirt-maintainers] Bug#1104735: Bug#1104735: libvirt: cannot restore internal snapshots In-Reply-To: <20250603183159.ncusv2okjrf7r2hf@meyneth> References: <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> <20250601161255.cst3bxyh5qcqrvfg@meyneth> <20250603183159.ncusv2okjrf7r2hf@meyneth> <0331ecf2-d9bc-45f8-9113-0fc06bc0f3f0@torproject.org> Message-ID: <3699606.ECZNHGQPT7@tuxin> Hey, Thanks a lot for this fast round trip and many thanks that the new version already entered unstable. > in the unblock bug I got the following request[1]: > > Please go ahead with the upload and remove the moreinfo tag from > > this unblock request once the new upload has been in unstable for a > > few days, and has been confirmed to fix the issue. > > When you get a chance this week, can you please confirm that the > package that was uploaded to unstable fixes that issue for you? I'm not the person you found this issue or know how to reproduce it easily. I asked my tails team mate anonym to check the new version. Hopefully they are fast enough to do it this week :) Just for reference the tails bugtracker: https://gitlab.tails.boum.org/tails/tails/-/issues/20932#note_261610 Regards, hefee -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: