Bug 2426854

Summary: ddrescue-1.30 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: ddrescueAssignee: Michal Ambroz <rebus>
Status: ON_QA --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: andreas, rebus, rhbugs, susi.lehtola
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Update to 1.30 (#2426854) none

Description Upstream Release Monitoring 2026-01-02 19:55:25 UTC 
Releases retrieved: 1.30
Upstream release that is considered latest: 1.30
Current version/release in rawhide: 1.29.1-2.fc43
URL: http://www.gnu.org/software/ddrescue/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/410/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddrescue
Comment 1 Upstream Release Monitoring 2026-01-02 19:57:41 UTC 
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-fm9o36v1/ddrescue.spec']' returned non-zero exit status 1.

StdOut:
setting SOURCE_DATE_EPOCH=1767312000
error: Bad file: ./ddrescue-1.30.tar.lz.sig: No such file or directory
error: Bad file: ./ddrescue-1.30.tar.lz: No such file or directory

RPM build errors:
    Bad file: ./ddrescue-1.30.tar.lz.sig: No such file or directory
    Bad file: ./ddrescue-1.30.tar.lz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.12/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues
Comment 2 Upstream Release Monitoring 2026-01-02 19:57:43 UTC 
Created attachment 2120861 [details]
Update to 1.30 (#2426854)
Comment 3 Fedora Update System 2026-01-04 16:32:37 UTC 
FEDORA-2026-305cd70b9c (ddrescue-1.30-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-305cd70b9c
Comment 4 Fedora Update System 2026-01-04 16:32:38 UTC 
FEDORA-EPEL-2026-fa0ea533f3 (ddrescue-1.30-2.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-fa0ea533f3
Comment 5 Fedora Update System 2026-01-04 16:32:38 UTC 
FEDORA-EPEL-2026-214a3de232 (ddrescue-1.30-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-214a3de232
Comment 6 Fedora Update System 2026-01-05 00:39:44 UTC 
FEDORA-2026-e632cd741c has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-e632cd741c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-e632cd741c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2026-01-05 00:46:14 UTC 
FEDORA-EPEL-2026-08f05a20e1 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-08f05a20e1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2026-01-05 00:52:10 UTC 
FEDORA-EPEL-2026-214a3de232 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-214a3de232

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 9 Fedora Update System 2026-01-05 01:02:56 UTC 
FEDORA-EPEL-2026-fa0ea533f3 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-fa0ea533f3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 10 Fedora Update System 2026-01-05 01:03:25 UTC 
FEDORA-2026-305cd70b9c has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-305cd70b9c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-305cd70b9c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.