Your message dated Wed, 16 Apr 2025 09:50:26 +0000 with message-id <E1u4zPW-00Cnoz-5a@fasolo.debian.org> and subject line Bug#1103297: fixed in zsync 0.6.2-8 has caused the Debian Bug report #1103297, regarding zsync: "failed to retrieve" with input file 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.) -- 1103297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103297 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: zsync: "failed to retrieve" with input file
- From: Ural Tunaboyu <ural.tunaboyu@canonical.com>
- Date: Wed, 16 Apr 2025 09:51:23 +0100
- Message-id: <[🔎] CAP1a3ueknL8evBLS03jD0f8hEftnq--NvOf_F9Uc4jUOGZF2Nw@mail.gmail.com>
Source: zsync Version: 0.6.2-7 Severity: important Downloading with the -i option fails with a "failed to retrieve" error: # zsync http://cdimage.ubuntu.com/ubuntu-base/noble/daily/current/noble-base-amd64.tar.gz.zsync -i noble-base-amd64.tar.gz #################### 100.0% 0 Bps DONE Read noble-base-amd64.tar.gz. Target 99.8% complete. ************** downloading from http://cdimage.ubuntu.com/ubuntu-base/noble/daily/current/noble-base-amd64.tar.gz: #################### 100.0% DONE failed to retrieve from noble-base-amd64.tar.gz Aborting, download available in noble-base-amd64.tar.gz.part verifying download... A revert to 0.6.2-6 fixes the problem.
--- End Message ---
--- Begin Message ---
- To: 1103297-close@bugs.debian.org
- Subject: Bug#1103297: fixed in zsync 0.6.2-8
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Wed, 16 Apr 2025 09:50:26 +0000
- Message-id: <E1u4zPW-00Cnoz-5a@fasolo.debian.org>
- Reply-to: Ural Tunaboyu <ural.tunaboyu@canonical.com>
Source: zsync Source-Version: 0.6.2-8 Done: Ural Tunaboyu <ural.tunaboyu@canonical.com> We believe that the bug you reported is fixed in the latest version of zsync, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1103297@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ural Tunaboyu <ural.tunaboyu@canonical.com> (supplier of updated zsync package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 16 Apr 2025 09:52:07 +0100 Source: zsync Built-For-Profiles: noudeb Architecture: source Version: 0.6.2-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packages@qa.debian.org> Changed-By: Ural Tunaboyu <ural.tunaboyu@canonical.com> Closes: 1103297 1103298 Changes: zsync (0.6.2-8) unstable; urgency=medium . * QA upload. * Revert to 0.6.2-6. (Closes: #1103297, #1103298) Checksums-Sha1: f43ed70b6ceabf97db2c1ca37a66a29d8536f35d 1789 zsync_0.6.2-8.dsc f9851038f1a7c9f5ac4d33361cffe188a73b5009 9432 zsync_0.6.2-8.debian.tar.xz Checksums-Sha256: 7662a37c5e4c4124a614ff771df05ae851f672aedd6a999086071b7da1334d61 1789 zsync_0.6.2-8.dsc 026ec8a91cecd31ebf35ae8d2e7fc25af2e532afd6870518d99d3c43a1222b6a 9432 zsync_0.6.2-8.debian.tar.xz Files: b03ee868c68631d9a4ca411c44cf24de 1789 net optional zsync_0.6.2-8.dsc ffd8456a14018c70611ae9620bbc91db 9432 net optional zsync_0.6.2-8.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmf/eXgACgkQr8/sjmac 4cLztxAAupsnz0wzCkiAhfyNMqlgzQTnz1CmuIQVVf13gCukBFczquauPNWhPUGL 1lMipY10OZcf+7BCt9PJFQDD7NAtp0P28E2oH1u3QxcKHNVVZwZ6+X+yo25iP6go 1sLTnNhPnBw/UJ0Wgnxg3kttvDVf7reHyn1KshmKtq2dljs6EUnMgFzu3TaKl509 WIXf+Gsk1dl4tKJNj2T6kRreK2isdEIgQ4dYJG6GDdMIIeKKMWTpsXWdd0MQ2BQ+ kw/TlId4v5WlI++9WJEvdbWPrkC7DPU6nS27Hphdf1chxY9uhIe0NwHCAQMbi6zp 4UONpxH6EIBqJM5kRSVuysKqxJRvHRHJQvDL38mwLgZFmkI5E4vlIlEgGYtUGOev k5uqnKgjeM7ba/18Uy0ToV+J3/8pBC8r5lvjmKpwKqO9wfui56W7yGYBdqkGQhq3 a5Y09m/XZPIER6R+ojBJlrsVTZmR3/w5z1nPufK/uNUk5SXd7dTUJ1dGY8Tpch8B zXy4jLEzKaKNzf78uXtBcw0YMzkktpyKVc3TsMjJEX8yJ7DwL71eubSRAlnCa8+/ WgFuarhkbpOJ0jMmzYSqJkfgGFCIZJKLb5g8fjiPMnvNRu3azt8lEIer4A/lU9dU ee1hwbnjKWaqVFUOm6nfmbE5RY9khfojM+ieLITNJWq/NQ2/J9U= =4GpD -----END PGP SIGNATURE-----Attachment: pgpxhadz0KLKh.pgp
Description: PGP signature
--- End Message ---