Description of problem: when installing borgbackup, python3-llfuse might not get installed by default. When python3-llfuse package is installed borg backup can mount backups as fuse filesystems. Recommending or requiring the package from within the .spec would be useful. Version-Release number of selected component (if applicable): 1.0.0-1 How reproducible: Maybe whenever one installs borgbackup and python3-llfuse is not already installed Steps to Reproduce: 1. dnf install borgbackup (note I used rpm to install the build, so this might actually already work.) Actual results: python3-llfuse is not automatically installed with borgbackup Expected results: python3-llfuse getting installed with borgbackup Additional info:
Hi, Thank you for your report. I will add the dependencies to make fuse mounts work out of the box.
borgbackup-1.0.0-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e9bd5cf00b
borgbackup-1.0.0-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-05a0787f3c
borgbackup-1.0.0-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e9bd5cf00b
borgbackup-1.0.0-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-05a0787f3c
borgbackup-1.0.0-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
borgbackup-1.0.0-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.