From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] ddrescue: Update to version 1.29
Date: Wed, 22 Jan 2025 13:43:04 +0100 [thread overview]
Message-ID: <20250122124315.14489-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2988 bytes --]
- Update from version 1.28 to 1.29
- Update of rootfile not required
- Changelog
1.29
The new option '--continue-on-errno' has been added.
If ddrescue exits because of a fatal read error, it now prints the value of
the variable 'errno' so that it can be used as argument to
'--continue-on-errno'.
When using '--ask' and '--verbose', print rescue options before asking user.
Option '--log-reads' now records the value of errno if different from EIO.
(The four changes above suggested by Christian Franke).
The effect of option '-O, --reopen-on-error' has been extended to all phases.
It has been documented in the manual that '--reopen-on-error' may be needed
when using '--continue-on-errno'.
A compilation error on FiwixOS 3.3 about an ambiguous call to std::abs has
been fixed. (Reported by Jordi Sanfeliu).
The chapter 'Syntax of command-line arguments' has been added to the manual.
Two examples of combined use with lziprecover have been added to the manual.
(One of them uses the new Forward Error Correction (FEC) feature of
lziprecover).
It has been documented in the manual that option '-b' of ddrescuelog is
position dependent. (Reported by Winston B. E.).
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/ddrescue | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lfs/ddrescue b/lfs/ddrescue
index 9d1c08fe2..8320751ae 100644
--- a/lfs/ddrescue
+++ b/lfs/ddrescue
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2024 IPFire Team <info(a)ipfire.org> #
+# Copyright (C) 2007-2025 IPFire Team <info(a)ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -26,7 +26,7 @@ include Config
SUMMARY = Data Copying in the Presence of I/O Errors
-VER = 1.28
+VER = 1.29
THISAPP = ddrescue-$(VER)
DL_FILE = $(THISAPP).tar.lz
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = ddrescue
-PAK_VER = 4
+PAK_VER = 5
DEPS =
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 8c212f0d495e0df8e0398b97730c812ea9ccb77bd42e730198222e9918e3652fc52d932449b1e0dc9bdd453a123e2450c962e33e98d9845ce81b9a934a5bbdaa
+$(DL_FILE)_BLAKE2 = 88eab69f2296464859dc8720930f28f6bc32aa694649e15a99dcd9dfd63ed8ba845d7af347e8b1ee90e954f8317888ec0f2cd90ec98994a7d2b4d654a31adbfc
install : $(TARGET)
--
2.48.1
next reply other threads:[~2025-01-22 12:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 12:43 Adolf Belka [this message]
2025-01-22 12:43 ` [PATCH] fontconfig: Update to version 2.16.0 Adolf Belka
2025-01-22 12:43 ` [PATCH] gdb: Update to version 16.1 Adolf Belka
2025-01-22 12:43 ` [PATCH] git: Update to version 2.48.1 Adolf Belka
2025-01-22 12:43 ` [PATCH] harfbuzz: Update to version 10.2.0 Adolf Belka
2025-01-22 12:43 ` [PATCH] libexif: Update to version 0.6.25 Adolf Belka
2025-01-22 12:43 ` [PATCH] libxcrypt: Update to version 4.4.38 Adolf Belka
2025-02-22 13:40 ` Michael Tremer
2025-02-23 18:04 ` Adolf Belka
2025-02-24 10:30 ` Michael Tremer
2025-01-22 12:43 ` [PATCH] lvm2: Update to version 2.03.30 Adolf Belka
2025-01-22 12:43 ` [PATCH] lynis: Update to version 3.1.3 Adolf Belka
2025-01-22 12:43 ` [PATCH] monit: Update to version 5.34.4 Adolf Belka
2025-01-22 12:43 ` [PATCH] openvmtools: Update to version 12.5.0 Adolf Belka
2025-01-22 12:43 ` [PATCH] pango: Update to version 1.56.1 Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250122124315.14489-1-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox