Bug 2068479
| Summary: | duply does not work with duplicity 0.8.22 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Schieschke <michael.schieschke> |
| Component: | duply | Assignee: | Thomas Moschny <thomas.moschny> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 35 | CC: | alex, laolux, thomas.moschny |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | duply-2.4-1.fc34 duply-2.4-1.fc35 duply-2.4-1.fc36 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-04-17 22:21:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Thanks for the report. Going to open an upstream ticket. As I don't think the issue is sensitive, lifting the group constraint. *** Bug 2066567 has been marked as a duplicate of this bug. *** Could you add a temporary patch so that duply is still usable? Thanks. @zhangalexy For a temporary workaround, use the development version of duply 2.4, which currently can be found here: http://duply.net/tmp/duply.sh Replace your /usr/bin/duply with that file and set the correct permissions, and you should be good to go. Note: messing with files from rpm packages can lead to issues down the road, but you wanted a temporary workaround, and this one works for me. Also note: The file on the link might quickly change. I don't know how to provide you with a better source. For reference, the version I am using has sha256 hash bca746b9a635cbe4467a30de77b32239996bbedc3b32fa43941c1ee8e9d536de Good luck! FEDORA-2022-8a5437f246 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8a5437f246 FEDORA-2022-1c6fffaa4e has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1c6fffaa4e FEDORA-2022-46378fb459 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-46378fb459 FEDORA-2022-1c6fffaa4e has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-1c6fffaa4e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1c6fffaa4e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-46378fb459 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-46378fb459` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-46378fb459 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-8a5437f246 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-8a5437f246` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8a5437f246 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-8a5437f246 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-46378fb459 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-1c6fffaa4e has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |
Description of problem: "duply" fails with duplicity duplicity 0.8.22 Version-Release number of selected component (if applicable): 2.3.1 How reproducible: Install package, create a profile, check status of that profile. Steps to Reproduce: 1. # dnf install duply 2. # duply /etc/duply/foo create 3. # duply /etc/duply/foo status Actual results: --- Start duply v2.3.1, time is 2022-03-25 09:45:55. Sorry. A fatal ERROR occured: /usr/bin/python3 -s missing. installed und available in path? PATH='/root/.local/bin:/root/bin:/usr/lib64/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin' --- Expected results: --- Start duply v2.3.1, time is 2022-03-25 13:48:14. Using profile '/etc/duply/foo'. Using installed duplicity version 0.8.17, python 3.9.2 (/usr/bin/python3), gpg 2.2.27 (Home: /root/.gnupg), awk 'GNU Awk 5.1.0, API: 3.0 (GNU MPFR 4.1.0, GNU MP 6.2.1)', grep 'grep (GNU grep) 3.6', bash '5.1.4(1)-release (x86_64-pc-linux-gnu)'. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - En/Decryption skipped. (GPG='disabled') --- Start running command STATUS at 13:48:14.677 --- [...] --- Finished state OK at 13:48:15.110 - Runtime 00:00:00.433 --- --- Additional info: The issue seems to be in function duplicity_python_binary_parse, from line 1182. This breaks with the shebang in duplicity 0.8.22 #!/usr/bin/python3 -s While in older versions (were duply works) it is something like #!/usr/bin/python3 Suggested change: Replace line 1188 from current DUPL_PYTHON_BIN=$(awk 'NR==1&&/^#!/{sub(/^#!( *\/usr\/bin\/env *)?/,""); print}' < "$DUPL_BIN") with something along DUPL_PYTHON_BIN=$(awk 'NR==1&&/^#!/{sub(/^#!( *\/usr\/bin\/env *)?/,""); print $1}' < "$DUPL_BIN") Note! I am not good at AWK, so this may be a stupid idea.