Checking: datarecovery-0.1.1-1.fc43.noarch.rpm datarecovery-0.1.1-1.fc43.src.rpm ============================ rpmlint session starts ============================ rpmlint: 2.8.0 configuration: /usr/lib/python3.13/site-packages/rpmlint/configdefaults.toml /etc/xdg/rpmlint/fedora-spdx-licenses.toml /etc/xdg/rpmlint/fedora.toml /etc/xdg/rpmlint/scoring.toml /etc/xdg/rpmlint/users-groups.toml /etc/xdg/rpmlint/warn-on-functions.toml rpmlintrc: [PosixPath('/tmp/tmpevrcedwj')] checks: 32, packages: 2 datarecovery.noarch: E: spelling-error ('ddrescue', '%description -l en_US ddrescue -> dd rescue, dd-rescue, rescuer') datarecovery.noarch: E: spelling-error ('rdfind', '%description -l en_US rdfind -> rd find, rd-find, find') datarecovery.src: E: spelling-error ('ddrescue', '%description -l en_US ddrescue -> dd rescue, dd-rescue, rescuer') datarecovery.src: E: spelling-error ('rdfind', '%description -l en_US rdfind -> rd find, rd-find, find') datarecovery.spec: W: specfile-warning warning: bogus date in %changelog: Fri Nov 22 2025 koxt2 - 0.1.1-1 datarecovery.spec: W: specfile-warning warning: bogus date in %changelog: Wed Nov 20 2025 koxt2 - 0.1.0-1 datarecovery.noarch: E: non-standard-executable-perm /usr/bin/datarecovery 555 datarecovery.noarch: W: no-manual-page-for-binary datarecovery datarecovery.noarch: W: no-manual-page-for-binary datarecovery-pkexec-helper datarecovery.noarch: E: incorrect-fsf-address /usr/bin/datarecovery datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/about.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/block_devices.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/config.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/device_columnview.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/device_dropdown.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/duplicates.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/file_operations.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/imager.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/initialiser.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/log.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/main.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/mounted_check.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/partition_guids.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/recover.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/recovery_dialog.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/recovery_workflow.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/settings.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/datarecovery/datarecovery/window.py datarecovery.noarch: E: incorrect-fsf-address /usr/share/licenses/datarecovery/LICENSE datarecovery.noarch: E: explicit-lib-dependency libadwaita 2 packages and 0 specfiles checked; 26 errors, 4 warnings, 7 filtered, 26 badness; has taken 0.2 s