Bug 999842
| Summary: | 'Backup Failed' message when external backup drive first inserted | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jonathan <emailjonathananderson-fedora> |
| Component: | deja-dup | Assignee: | Gwyn Ciesla <gwync> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | emailjonathananderson-fedora, fedora, jitesh.1337, kengert, metherid, mike, mnowak, scott.holistic, ville.skytta |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-20 12:41:21 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: | |||
|
Description
Jonathan
2013-08-22 09:05:20 UTC
still a problem in F19. deja-dup.x86_64 26.0-1.fc19 Would you mind reporting this upstream at https://launchpad.net/deja-dup It's reported https://bugs.launchpad.net/deja-dup/+bug/1062186 Try http://koji.fedoraproject.org/koji/taskinfo?taskID=6728739 If you are using Fedora 20, https://admin.fedoraproject.org/updates/deja-dup-30.0-1.fc20 Updated duplicity and DejaDup but got "Could not understand duplicity version.". Perhaps it will work after restart. Yeah. Keep me posted on which Fedora version you are using as well One also needs to install python-lockfile otherwise:
~ $ deja-dup --backup
Traceback (most recent call last):
File "/usr/bin/duplicity", line 34, in <module>
from lockfile import FileLock
ImportError: No module named lockfile
(Interestingly ABRT won't catch it.)
~ $ rpmquery deja-dup duplicity
deja-dup-30.0-1.fc20.x86_64
duplicity-0.6.23-1.fc20.x86_64
Thought the bug 999842 is not fixed yet, still getting: "An operation is already pending".
The lockfile issue is already fixed (1086848). I will reset the status This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Yes, this bug is still here unchanged. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Confirm still get the error in Fedora 24. Does installing python-lockfile still correct the issue? I have python-lockfile installed and always had it on F-23 and it does not correct the originally reported issue for me (so the "still" doesn't apply at least here). Reported upstream: https://bugs.launchpad.net/deja-dup/+bug/1619294 This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |