[Desktop-packages] [Bug 929067] Re: Crash during restore: "assert ropath.index == (), ropath.index"
If you install via pip, be sure to remove the pkg first. Different install locations will cause problems. See https://gitlab.com/duplicity/duplicity. We moved years ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/929067 Title: Crash during restore: "assert ropath.index == (), ropath.index" Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Released Bug description: Duplicity version: 0.6.15 Python version: 2.7.2+ OS: Ubuntu 11.10 Target filesystem: Linux (Synology NAS, via sftp) I'm experiencing a repeatable crash which manifests itself on restore, when the initial backup is interrupted and resumed. The data I use doesn't seem to matter. Steps to reproduce: 1. Create a directory of test data. Mine was around 125MiB 2. duplicity --no-encryption TestDir ssh://user@target/backup/TestDir 3. Wait until one or two tar files have been uploaded, then Ctrl-C to kill duplicity 4. duplicity --no-encryption TestDir ssh://user@target/backup/TestDir (duplicity should resume the backup where it left off; allow it to complete this time) 5. duplicity --no-encryption TestDir ssh://user@target/backup/TestDir (repeat the command a third time - note that duplicity reports a nonzero number of DeletedFiles even though the data has not changed. 6. rm -r TestDir 7. duplicity --no-encryption ssh://user@target/backup/TestDir TestDir (attempt to restore -> crash) The crash output is as follows: user@laptop:~$ duplicity --no-encryption ssh://user@target/backup/Test4 Test4 Local and Remote metadata are synchronized, no sync needed. Last full backup date: Wed Feb 8 19:29:16 2012 Traceback (most recent call last): File "/usr/bin/duplicity", line 1359, in with_tempdir(main) File "/usr/bin/duplicity", line 1342, in with_tempdir fn() File "/usr/bin/duplicity", line 1276, in main restore(col_stats) File "/usr/bin/duplicity", line 591, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in Write_ROPaths ITR( ropath.index, ropath ) File "/usr/lib/python2.7/dist-packages/duplicity/lazy.py", line 320, in __call__ self.process_w_branch(index, self.root_branch, args) File "/usr/lib/python2.7/dist-packages/duplicity/lazy.py", line 293, in process_w_branch branch.start_process, args) File "/usr/lib/python2.7/dist-packages/duplicity/robust.py", line 37, in check_common_error return function(*args) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 545, in start_process assert ropath.index == (), ropath.index AssertionError: somefile.dat I can provide more information, log output, test data (although the data doesn't seem to matter), or test with other versions of duplicity if requested. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/929067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051459] Re: duplicity missing from /usr/bin in current deb package.
See https://gitlab.com/duplicity/duplicity/-/issues/797 This is not a Ubuntu duplicity error, rather a GitLab duplicity error. We moved. ** Bug watch added: gitlab.com/duplicity/duplicity/-/issues #797 https://gitlab.com/duplicity/duplicity/-/issues/797 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/2051459 Title: duplicity missing from /usr/bin in current deb package. Status in duplicity package in Ubuntu: New Bug description: See: https://discourse.mailinabox.email/t/the-latest-release-of-duplicity-is-missing-the-duplicity-binary/11439 and https://discourse.mailinabox.email/t/backup-duplicity-error-file-not- found-backup-never-run/11438 Getting error: [Errno 2] No such file or directory: ‘/usr/bin/duplicity’ .../duplicity_2.2.0-ppa202401271616~ubuntu22.04.1_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/2051459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
BTW, bug reporting has moved to https://gitlab.com/duplicity/duplicity/-/issues. Please report an issue there if you're still having problems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
Hi David, This sounds like a mismatch in libraries which happens when multiple versions of duplicity are installed from different sources. I'd like you to do this: $ sudo apt purge duplicity# to remove the distro version. $ sudo python3 -m pip uninstall duplicity # to remove the pip3 version. $ sudo snap remove duplicity # to remove the snap version. You may get errors in any of those. That's OK. Then reinstall from Gitlab by doing: $ sudo python3 -m pip install https://gitlab.com/duplicity/duplicity/uploads/3e1efd3ebe74bbbf2109f3d9c239f4be/duplicity-2.1.3.tar.gz This is the versioned source from https://gitlab.com/duplicity/duplicity/-/releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1640558] Re: 16.10 Backup Failure.
I have not seen this before. Is it possible it's an Out Of Memory error? duplicity 0.7.06 is ancient and Python2.7 has been End Of Life for a couple of years. I would suggest looking into upgrading to duplicity 1.2.3, which is the last version that will support Python2.7. The easiest way is to: $ sudo apt remove duplicity <--- do not skip this step $ sudo python -m pip install duplicity==1.2.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1640558 Title: 16.10 Backup Failure. Status in duplicity package in Ubuntu: Expired Bug description: A daily backup job run by corn invokes a script that runs duplicity. Since I have upgraded to 16.10 from 16.04 duplicity crashes with the message "killed". It seems that the real problem is in the NVIDIA driver for my screen. The machine does not crash in other situations. Some info Dell XPS 15 L502X, 15,6" FHD, NVIDIA GEFORCE GT 540M GR 2 GB NVIDIA driver version 367.57 X server version 11.0, server vendor version 1.18.4, NV-control version 1.29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1640558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 510625] Re: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english.
** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/510625 Title: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english. Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Confirmed Status in duplicity package in Debian: Confirmed Bug description: this is a forward/extract of debian bug #565398, which lives over there: http://bugs.debian.org/565398 summary: when using gpg and --encrypt-key, and only if LANG is set to de_AT and LC_CTYPE is set to de_AT (or POSIX or C, but not iso-8859-1 or utf-8), then incremental backups fail completely. somehow or other duplicity mis-interprets gnupg output and errors out: i assume it would be the 8-bit nature of certain phrases like "Schlüssel" (german for "key") which causes the mess, but i can't identify the code in question. reproducible: always. needs only an empty backup dir (source), an empty target dir (target), a gpg key and locale de_AT available. duplicity --encrypt-key KEYID source file://target works fine, creates a (minuscule) full backup running it again, with LANG unset (or to something purely 7bit like en_US) works perfect again, no problems. but running it with LANG=de_AT and LC_CTYPE=de_AT causes duplicity to attempt some gnupg decryption (of what? the cache and archive are in sync), and it dies with a gpg failure (with the gpg message being the german equivalent of "encryption failed: bad passphrase", not surprising as no passphrase was given, nor should one be necessary). i'm attaching the relevant -v9 logs, first of the successful full run, then of a failed inc run (LANG and LC_CTYPE=de_AT) and then of the successful inc run (LANG="", LC_CTYPE=de_AT). no changes were made to the source dir between runs. regards, az To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/510625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 510625] Re: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english.
** Changed in: duplicity Milestone: None => 0.8.24 ** Changed in: duplicity Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/510625 Title: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english. Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Confirmed Status in duplicity package in Debian: Confirmed Bug description: this is a forward/extract of debian bug #565398, which lives over there: http://bugs.debian.org/565398 summary: when using gpg and --encrypt-key, and only if LANG is set to de_AT and LC_CTYPE is set to de_AT (or POSIX or C, but not iso-8859-1 or utf-8), then incremental backups fail completely. somehow or other duplicity mis-interprets gnupg output and errors out: i assume it would be the 8-bit nature of certain phrases like "Schlüssel" (german for "key") which causes the mess, but i can't identify the code in question. reproducible: always. needs only an empty backup dir (source), an empty target dir (target), a gpg key and locale de_AT available. duplicity --encrypt-key KEYID source file://target works fine, creates a (minuscule) full backup running it again, with LANG unset (or to something purely 7bit like en_US) works perfect again, no problems. but running it with LANG=de_AT and LC_CTYPE=de_AT causes duplicity to attempt some gnupg decryption (of what? the cache and archive are in sync), and it dies with a gpg failure (with the gpg message being the german equivalent of "encryption failed: bad passphrase", not surprising as no passphrase was given, nor should one be necessary). i'm attaching the relevant -v9 logs, first of the successful full run, then of a failed inc run (LANG and LC_CTYPE=de_AT) and then of the successful inc run (LANG="", LC_CTYPE=de_AT). no changes were made to the source dir between runs. regards, az To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/510625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875937] Re: Download of vol1 in validate_encryption_settings() fails when using S3 glacier
Yes, this was fixed for boto+s3, but then we changed the default for s3:// from boto to boto3. Boto3 does not support glacier yet, so you may just need to specify boto+s3:// instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1875937 Title: Download of vol1 in validate_encryption_settings() fails when using S3 glacier Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Bug description: Duplicity version: 0.8.12.1612 ubuntu 20.04 LTS python 3.8.2 When i try to restart a backup which goes to S3 (via boto3) (use of: --s3-use-deep-archive or --s3-use-glacier) it fails: Last full backup date: Wed Apr 29 17:45:32 2020 RESTART: Volumes 2 to 2 failed to upload before termination. Restarting backup at volume 2. Attempt 1 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class Attempt 2 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class This is because a file stored in glacier cannot be downloaded. I dont know if this known? To solve this: either skip validate_encryption_settings() when using any of this storage backends or introduce an option to skip the download manually (e.g. --skip-download-on-restart) I fixed it for me with manully skipping the validate_encryption_settings() function. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1875937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980908] Re: duplicity does NOT close properly
** Changed in: duplicity Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1980908 Title: duplicity does NOT close properly Status in Déjà Dup: Incomplete Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: New Bug description: Duplicity process stays running after closing deja-dup backups app from Ubuntu desktop. Openning up deja-dup again, go to Restore tab, error message shows "Another duplicity instance is already running with this archive directory". `ps -ef | grep duplicity` shows the process still running. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1980908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980908] Re: duplicity does NOT close properly
Also, how did you exit deja-dup? Clean exit or task killed? Is this repeatable? I don't have a Linux GUI to test on, just terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1980908 Title: duplicity does NOT close properly Status in Déjà Dup: New Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Duplicity process stays running after closing deja-dup backups app from Ubuntu desktop. Openning up deja-dup again, go to Restore tab, error message shows "Another duplicity instance is already running with this archive directory". `ps -ef | grep duplicity` shows the process still running. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1980908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980908] Re: duplicity does NOT close properly
Please provide some more info: - version number of duplicity and deja-dup - Python version running - OS version Also, how did you exit deja-dup? Clean exit or task killed? ** Also affects: duplicity Importance: Undecided Status: New ** Also affects: deja-dup Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1980908 Title: duplicity does NOT close properly Status in Déjà Dup: New Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Duplicity process stays running after closing deja-dup backups app from Ubuntu desktop. Openning up deja-dup again, go to Restore tab, error message shows "Another duplicity instance is already running with this archive directory". `ps -ef | grep duplicity` shows the process still running. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1980908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
Invalid
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
All systems run a bit strange if disk space runs out, most not too
gracefully. duplicity will estimate the space needed on the local
system to run duplicity, but cannot check the remote. It will fail with
whatever status the remote returns, which you should then correct if
possible. I don't know what caused your truncation, but the error
message should now be clearer and have the responsible filename in it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
Fix Committed
Status in duplicity package in Ubuntu:
Invalid
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
** Changed in: duplicity
Status: Confirmed => Fix Committed
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
Fix Committed
Status in duplicity package in Ubuntu:
Invalid
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
** Changed in: duplicity
Milestone: 0.8.24 => 0.8.23
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
Invalid
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
** Changed in: duplicity
Milestone: None => 0.8.24
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
Invalid
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
Whoops! You're right. I'm marking this as 'confirmed' and will fix the
error message to the correct filename.
** Changed in: duplicity
Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
Invalid
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
Whoops! You're right. I'm marking this as 'confirmed' and will fix the
error message to the correct filename.
** Changed in: duplicity
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
Invalid
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
Good catch on the script.
Looks like you've run afoul of two bugs, one in Samba and one in
duplicity:
1. https://bugs.launchpad.net/duplicity/+bug/385495 - no solution yet.
2. Google "samba large file size". Looks like 2GB is the limit. I
suspect the file was written on the last backup and samba simply
truncated it at 2GB. The only option suggested in what I read was to
mount the drive as in https://www.cyberciti.biz/faq/howto-access-files-
greater-than-2gb-samba, and samba will accept the LFS. There may be a
way to do it in config.
I would suggest mounting the drive with LFS enabled and rerunning the backup
after running
"duplicity cleanup --force ".
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
** Changed in: duplicity
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
Invalid
Status in duplicity package in Ubuntu:
New
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
Thank you for responding.
I'm convinced the error is a truncated .gz file, but duplicity is not
telling us which one. So, let's go to the source directly.
On your remote machine:
$ cd /home/scohen/Taormina
$ for f in *.gz; do echo "--- $f ---"; tar tzf $f; done
This will list the index of all the *.gz files and failure should
indicate which one is truncated. That file will be the one with '---
filename ---' prior to the error.
Then we can figure out what to do next.
** Changed in: duplicity
Status: New => In Progress
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
New
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
** Attachment removed: "log.head"
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1970124/+attachment/5585694/+files/log.head
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
New
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
I'd like a log file, please. This is going to be big and I only need a
portion. Please run duplicity with -v9, redirect to a log file, then
run:
$ head -n 200 < log > log.head
$ tail -n 200 < log > log.tail
Attach, do NOT copy/paste, log.head and log.tail to this bug report.
See green button below.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
New
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970124] Re: duplicity backup fails with obscure error message Ubuntu 22.04
** Also affects: duplicity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1970124
Title:
duplicity backup fails with obscure error message Ubuntu 22.04
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
New
Bug description:
I try to do a backup onto a network location (ssh://192.168.1.61 - I
can successfully connect to this location via ssh). The backup
completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-xdksj47v-tempdir/mktemp-_5khubio-2:
(, EOFError('Compressed file ended before the end-
of-stream marker was reached'), )
While the backup is running, we can see a duplicity* directory under
/tmp:
$ ll /tmp/duplicity-i6olpr17-tempdir/
total 16
drwx-- 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw--- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure
message.
A scan of the directory after the failure reveals no files like
/tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1970124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946717] Re: Giving up after 5 attempts. Error: Error reading from file: Invalid argument
OK, fat-fingered the post and now we continue... 2) if #1 shows duplicity backup files, please try the verify with the pexpect+sftp: schema rather than the files: schema to avoid gio. 3) please also provide the output of: $ python3 -c 'import sys; print(sys.getfilesystemencoding())' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1946717 Title: Giving up after 5 attempts. Error: Error reading from file: Invalid argument Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: Incomplete Bug description: After ask backup, the backup check failed To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1946717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946717] Re: Giving up after 5 attempts. Error: Error reading from file: Invalid argument
A couple more requests: 1) Please run: 'ls -l /var/run/user/220586/gvfs/smb-share\:server\=ealfsafestig423.pgs\,share\=bcq_gae/vincent.cieslak/backup' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1946717 Title: Giving up after 5 attempts. Error: Error reading from file: Invalid argument Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: Incomplete Bug description: After ask backup, the backup check failed To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1946717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946717] Re: Giving up after 5 attempts. Error: Error reading from file: Invalid argument
I'd like a log file, please. This is going to be big and I only need a portion. Please run duplicity with -v9, redirect to a log file, then run: $ head -n 200 < log > log.head $ tail -n 200 < log > log.tail Attach, do NOT copy/paste, log.head and log.tail to this bug report. See green button below. ** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1946717 Title: Giving up after 5 attempts. Error: Error reading from file: Invalid argument Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: New Bug description: After ask backup, the backup check failed To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1946717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743247] Re: B2 Python APIs are missing
Two options for now: - upgrade to the _latest_ (dev) version of duplicity, - revert to b2sdk==1.7.0 until duplicity 0.8.20 is released To revert do: _sudo pip install -U b2sdk==1.7.0_ There are multiple options for latest: - Latest snap builds - “sudo snap install duplicity —classic —edge" - Latest pip3 builds - “sudo pip3 install --pre duplicity" - Latest duplicity PPA - https://code.launchpad.net/\~duplicity-team/+archive/ubuntu/duplicity-develop-git Note 1: UNINSTALL duplicity first if it was installed from a different source.. This is due to divergent install locations, especially between repository installs and the other forms. Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10, Focal 20.04, Hirsute 20.10 and Impish 21.04. Note 3: Xenial 16.04 works with Snap and Pip installs, but cannot be built under Launchpad PPAs at the moment. ** Changed in: duplicity Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1743247 Title: B2 Python APIs are missing Status in Duplicity: Invalid Status in duplicity package in Ubuntu: Confirmed Bug description: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1743247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933540] Re: duplicity falsely reports B2 python SDK not installed, fails backup to B2
** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1933540 Title: duplicity falsely reports B2 python SDK not installed, fails backup to B2 Status in Duplicity: New Status in duplicity package in Ubuntu: Invalid Bug description: Description: Ubuntu 21.04 Release: 21.04 duplicity: Installed: 0.8.17-1build1 Candidate: 0.8.17-1build1 Version table: *** 0.8.17-1build1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: duplicity successfully backs up to B2 when I run `duplicity ~ b2://@` What happened instead: duplicity immediately fails with the error "BackendException: B2 backend requires B2 Python SDK (pip install b2sdk)". duplicity was working fine for me backing up my local machine to BackBlaze B2, when I was running 20.10. After upgrading to 21.04, now I get this problem. Both b2 and b2sdk are installed by pip and pip3, with and without sudo. I do use pyenv to manage different Python versions but pyenv global is set to system when I use pip to try to troubleshoot this, so this should not be interfering ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: duplicity 0.8.17-1build1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Jun 24 12:28:50 2021 InstallationDate: Installed on 2020-11-20 (215 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: Upgraded to hirsute on 2021-06-15 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1933540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933540] Re: duplicity falsely reports B2 python SDK not installed, fails backup to B2
Two options for now: - upgrade to the _latest_ (dev) version of duplicity, - revert to b2sdk==1.7.0 until duplicity 0.8.20 is released To revert do: _sudo pip install -U b2sdk==1.7.0_ There are multiple options for latest: - Latest snap builds - “sudo snap install duplicity —classic —edge" - Latest pip3 builds - “sudo pip3 install --pre duplicity" - Latest duplicity PPA - https://code.launchpad.net/\~duplicity-team/+archive/ubuntu/duplicity-develop-git Note 1: UNINSTALL duplicity first if it was installed from a different source.. This is due to divergent install locations, especially between repository installs and the other forms. Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10, Focal 20.04, Hirsute 20.10 and Impish 21.04. Note 3: Xenial 16.04 works with Snap and Pip installs, but cannot be built under Launchpad PPAs at the moment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1933540 Title: duplicity falsely reports B2 python SDK not installed, fails backup to B2 Status in Duplicity: New Status in duplicity package in Ubuntu: Invalid Bug description: Description: Ubuntu 21.04 Release: 21.04 duplicity: Installed: 0.8.17-1build1 Candidate: 0.8.17-1build1 Version table: *** 0.8.17-1build1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: duplicity successfully backs up to B2 when I run `duplicity ~ b2://@` What happened instead: duplicity immediately fails with the error "BackendException: B2 backend requires B2 Python SDK (pip install b2sdk)". duplicity was working fine for me backing up my local machine to BackBlaze B2, when I was running 20.10. After upgrading to 21.04, now I get this problem. Both b2 and b2sdk are installed by pip and pip3, with and without sudo. I do use pyenv to manage different Python versions but pyenv global is set to system when I use pip to try to troubleshoot this, so this should not be interfering ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: duplicity 0.8.17-1build1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Thu Jun 24 12:28:50 2021 InstallationDate: Installed on 2020-11-20 (215 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: Upgraded to hirsute on 2021-06-15 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1933540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 487720] Re: Restore fails with "Invalid data - SHA1 hash mismatch"
Please upgrade to the current version of duplicity. If you can reliably reproduce this bug, please let me know what you did, in detail, with attached -v9 log files and minimal munging. DO NOT copy/paste log files here. They are impossible to read. I took the script in the bug description section, modified it to use verify instead of the check kludge, and have been unable to reproduce it after many runs. It still fails to verify this bug. There are multiple options both stable and latest: - Stable snap builds - “sudo snap install duplicity —classic" - Latest snap builds - “sudo snap install duplicity —classic —edge" - Stable pip3 builds - “sudo pip3 install duplicity" - Latest pip3 builds - “sudo pip3 install --pre duplicity" - Stable duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-release-git - Latest duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-develop-git - Stable tarball install - https://launchpad.net/duplicity/+download - Source - https://gitlab.com/duplicity/duplicity Note 1: UNINSTALL duplicity first if it was installed from a different source.. This is due to divergent install locations, especially between repository installs and the other forms. Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10, Focal 20.04, Hirsute 20.10 and Impish 21.04. Note 3: Xenial 16.04 works with Snap and Pip installs, but cannot be built under Launchpad PPAs at the moment. ** Changed in: duplicity Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/487720 Title: Restore fails with "Invalid data - SHA1 hash mismatch" Status in Déjà Dup: Invalid Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: Fix Released Status in duplicity source package in Lucid: Fix Released Status in duplicity source package in Maverick: Won't Fix Status in duplicity source package in Natty: Fix Released Bug description: When restoring a backup, one might see an error like: Invalid data - SHA1 hash mismatch: Calculated hash: 0b2bc4c2fb98b36f9891f9172f909d70ab5662e9 Manifest hash: 11cd330357618de52e4e5361a6e63b09ee951ae2 This can happen when a volume file was not completely written to the backend before duplicity was interrupted (say, shutting down the machine or whatever). When duplicity resumes the backup next run, it will start with the next volume. The half-complete volume file will sit on the backend and cause this error later when restoring. You can manually recover from this by either restoring from your older backup sets or by restoring individual files that don't happen to be in the corrupted volume. == To Reproduce == See attachment https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/487720/+attachment/2159465/+files/test.sh for a test script tor reproduce the problem. == Ubuntu SRU Justification == This is a serious data loss problem for users, which won't be noticed until they try to restore. With Ubuntu 11.10 including Deja Dup, some users may think to back up their data first then upgrade, and may accidentally create corrupted backups. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/487720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 487720] Re: Restore fails with "Invalid data - SHA1 hash mismatch"
I need to find a reproducible scenario. There are hardware reasons for network transfers to drop bits and there are software reasons for the problem. I think we are seeing a mix of both. I've had downloads fail when going through a non-parity checking router, so that's one for hardware. I've yet to reproduce it in a reliable scenario with just software. ** Changed in: duplicity Importance: Medium => High ** Changed in: duplicity Status: Fix Released => Confirmed ** Changed in: duplicity Milestone: 0.6.14 => None ** Changed in: duplicity Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/487720 Title: Restore fails with "Invalid data - SHA1 hash mismatch" Status in Déjà Dup: Invalid Status in Duplicity: Confirmed Status in duplicity package in Ubuntu: Fix Released Status in duplicity source package in Lucid: Fix Released Status in duplicity source package in Maverick: Won't Fix Status in duplicity source package in Natty: Fix Released Bug description: When restoring a backup, one might see an error like: Invalid data - SHA1 hash mismatch: Calculated hash: 0b2bc4c2fb98b36f9891f9172f909d70ab5662e9 Manifest hash: 11cd330357618de52e4e5361a6e63b09ee951ae2 This can happen when a volume file was not completely written to the backend before duplicity was interrupted (say, shutting down the machine or whatever). When duplicity resumes the backup next run, it will start with the next volume. The half-complete volume file will sit on the backend and cause this error later when restoring. You can manually recover from this by either restoring from your older backup sets or by restoring individual files that don't happen to be in the corrupted volume. == To Reproduce == See attachment https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/487720/+attachment/2159465/+files/test.sh for a test script tor reproduce the problem. == Ubuntu SRU Justification == This is a serious data loss problem for users, which won't be noticed until they try to restore. With Ubuntu 11.10 including Deja Dup, some users may think to back up their data first then upgrade, and may accidentally create corrupted backups. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/487720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
Thanks for your patience with this! ** Changed in: duplicity Status: In Progress => Invalid ** Changed in: duplicity Milestone: 0.8.20 => None ** Changed in: duplicity Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: Invalid Status in duplicity package in Ubuntu: New Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(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 PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_art
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
See previous. Also, please read the comments here: https://www.google.com/search?q=botocore.exceptions.ClientError%3A+An+error+occurred+(403)+when+calling+the+HeadBucket+operation%3A+Forbidden&oq=botocore.exceptions.ClientError%3A+An+error+occurred+(403)+when+calling+the+HeadBucket+operation%3A+Forbidden&aqs=chrome..69i57&sourceid=chrome&ie=UTF-8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: In Progress Status in duplicity package in Ubuntu: New Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(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 PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_arti
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
Are there any funny or escaped characters in BUCKET_NAME (from the first log/traceback)? We pass the URL as a unicode string. Somehow boto/urllib thinks its a byte string. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: In Progress Status in duplicity package in Ubuntu: New Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(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 PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption --verbosity 9 --full-if-older-than 7D --volsize 1024 --s3-use-multiprocessing --s3-multipart-chunk-size 512 --allow-source-mismatch --exclude-fi
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
** Changed in: duplicity (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: In Progress Status in duplicity package in Ubuntu: New Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(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 PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption --verbosity 9 --full-if-older-than 7D --volsize 1024 --s3-use-multiprocessing --s3-multipart-chunk-size 512 --allow-source-mismatch --exclude-filelist /root/.duply/artifactory_backup/exclude /MyDirectory s3://s3-us-west-2.amazonaws.com/BUCKET-NAME/
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
** Changed in: duplicity (Ubuntu) Status: Incomplete => In Progress ** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Status: New => In Progress ** Changed in: duplicity Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman) ** Changed in: duplicity Milestone: None => 0.8.20 ** Changed in: duplicity Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: In Progress Status in duplicity package in Ubuntu: New Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(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 PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main a
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
Yes, it should be urllib3. We keep the older boto+s3:// around because it is still needed. Try using the boto3+s3:// backend instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in duplicity package in Ubuntu: Incomplete Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(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 PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption --verbosity 9 --full-if-older-than 7D --volsize 1024 --s3-use-multiprocessing --s3-multipart-chunk-size 512 --allow-source-mismatch --exclude-filelist /root/.duply/artifactory_backup/exclude /MyDirectory s3:/
[Desktop-packages] [Bug 1930640] Re: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object
It's not in duplicity, but in urllib. Do this to upgrade all modules we use: $ sudo python3 -m pip install -U -r requirements.txt where requirements.txt is from: https://git.launchpad.net/duplicity/plain/requirements.txt Let me know how it goes. ** Changed in: duplicity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930640 Title: Error when using S3 multipart upload - TypeError: cannot use a string pattern on a bytes-like object Status in duplicity package in Ubuntu: Incomplete Bug description: I followed the solution in https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19, the problem still persists for me when trying to use S3 multipart uploads. Note: This problem doesn't appear to exist in duplicity 0.7.17 running on python2.7, which is making me wonder if this is a python3.8 related issue. user@host:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.19-ppa202104291804~ubuntu20.04.1 Candidate: 0.8.19-ppa202104291804~ubuntu20.04.1 Version table: *** 0.8.19-ppa202104291804~ubuntu20.04.1 500 500 http://ppa.launchpad.net/duplicity-team/duplicity-release-git/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 0.8.11.1612-1 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages Start duply v2.2, time is 2021-06-02 22:58:11. Using profile '/root/.duply/artifactory_backup'. Using installed duplicity version 0.8.19, python 3.8.5 (/usr/bin/python3), gpg 2.2.19 (Home: /root/.gnupg), awk 'GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.0.2, GNU MP 6.2.0)', grep 'grep (GNU grep) 3.4', bash '5.0.17(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 PRE at 22:58:11.550 --- Skipping n/a script '/root/.duply/artifactory_backup/pre'. --- Finished state OK at 22:58:11.563 - Runtime 00:00:00.013 --- --- Start running command BKP at 22:58:11.595 --- Using archive dir: /root/.cache/duplicity/duply_artifactory_backup Using backup name: duply_artifactory_backup GPG binary is gpg, version (2, 2, 19) Import of duplicity.backends.adbackend Succeeded Import of duplicity.backends.azurebackend Succeeded Import of duplicity.backends.b2backend Succeeded Import of duplicity.backends.boxbackend Failed: No module named 'boxsdk' Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.gdrivebackend Succeeded Import of duplicity.backends.giobackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.hubicbackend Succeeded Import of duplicity.backends.idrivedbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.jottacloudbackend Succeeded Import of duplicity.backends.lftpbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.mediafirebackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.megav2backend Succeeded Import of duplicity.backends.megav3backend Succeeded Import of duplicity.backends.multibackend Succeeded Import of duplicity.backends.ncftpbackend Succeeded Import of duplicity.backends.onedrivebackend Succeeded Import of duplicity.backends.par2backend Succeeded Import of duplicity.backends.pcabackend Succeeded Import of duplicity.backends.pydrivebackend Succeeded Import of duplicity.backends.rclonebackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.s3_boto3_backend Succeeded Multiprocessing is not supported on linux, will use threads instead. Import of duplicity.backends.s3_boto_backend Succeeded Import of duplicity.backends.ssh_paramiko_backend Succeeded Import of duplicity.backends.ssh_pexpect_backend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.sxbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Setting multipart boto backend process pool to 4 processes Reading globbing filelist /root/.duply/artifactory_backup/exclude Main action: inc Acquiring lockfile b'/root/.cache/duplicity/duply_artifactory_backup/lockfile' duplicity 0.8.19 Args: /usr/bin/duplicity --name duply_artifactory_backup --no-encryption --verbosity 9 --ful
[Desktop-packages] [Bug 1930152] Re: duplicity 0.8.12 fails to complete backup
Please upgrade to the current version of duplicity, 0.8.19. This will assure that any bugs fixed since your release are available and may fix your issue. See Notes below. There are multiple options both stable and latest: - Stable snap builds - “sudo snap install duplicity —classic" - Latest snap builds - “sudo snap install duplicity —classic —edge" - Stable pip3 builds - “sudo pip3 install duplicity" - Latest pip3 builds - “sudo pip3 install --pre duplicity" - Stable duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-release-git - Latest duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-develop-git - Stable tarball install - https://launchpad.net/duplicity/+download - Source - https://gitlab.com/duplicity/duplicity Note 1: UNINSTALL duplicity first if it was installed from a different source.. This is due to divergent install locations, especially between repository installs and the other forms. Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10, Focal 20.04, Hirsute 20.10 and Impish 21.04. Note 3: Xenial 16.04 works with Snap and Pip installs, but cannot be built under Launchpad PPAs at the moment. ** Changed in: duplicity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1930152 Title: duplicity 0.8.12 fails to complete backup Status in duplicity package in Ubuntu: Incomplete Bug description: Distributor ID: Ubuntu Description: Ubuntu 20.10 Release: 20.10 Codename: groovy duplicity --version duplicity 0.8.12 This error started showing up about a week ago. Traceback (innermost last): File "/usr/bin/duplicity", line 106, in with_tempdir(main) File "/usr/bin/duplicity", line 92, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1538, in main do_backup(action) File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1662, in do_backup full_backup(col_stats) File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 559, in full_backup bytes_written = dummy_backup(tarblock_iter) File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 224, in dummy_backup while next(tarblock_iter): File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 544, in __next__ result = self.process(next(self.input_iter)) # pylint: disable=assignment-from-no-return File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 209, in get_delta_iter for new_path, sig_path in collated: File "/usr/lib/python3/dist-packages/duplicity/diffdir.py", line 310, in collate2iters for relem1 in riter1: File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 97, in __next__ return next(self.iter) File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 181, in Iterate subpath, val = next(diryield_stack[-1]) File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 148, in diryield s = self.Select(new_path) File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 210, in Select result = sf(path) File "/usr/lib/python3/dist-packages/duplicity/selection.py", line 458, in exclude_sel_func elif path.append(filename).exists(): File "/usr/lib/python3/dist-packages/duplicity/path.py", line 566, in append return self.__class__(self.base, self.index + (ext,)) File "/usr/lib/python3/dist-packages/duplicity/path.py", line 539, in __init__ self.setdata() File "/usr/lib/python3/dist-packages/duplicity/path.py", line 549, in setdata self.stat = os.lstat(self.name) PermissionError: [Errno 13] Permission denied: b'/home/dgd/.cache/qBittorrent/.deja-dup-ignore' ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: duplicity 0.8.11.1612-1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 30 12:06:15 2021 InstallationDate: Installed on 2015-08-23 (2106 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-01-13T09:36:03.851337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1930152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desk
[Desktop-packages] [Bug 1778638] Re: duplicity stuck in splice() call on Bionic
** Changed in: duplicity Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1778638 Title: duplicity stuck in splice() call on Bionic Status in Duplicity: Fix Released Status in deja-dup package in Ubuntu: Triaged Bug description: I am using Duplicity through Deja-Dup through its deja-dup-monitor process. After update to Bionic, it has basically stopped doing backups. Version is duplicity 0.7.17+bzr1357, Python version is 2.7.15rc1, Xubuntu Bionic. It seems to be stuck in pipes related call. When I try to strace the process I get this: strace: Process 28490 attached splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE From handle 9 to 16. The handle 9 is a file on my CIFS mount to where I do backups. If I go to the directory and do ls it works fine: duplicity 28490 USER9r REG 0,52 359 67128742 /var/backups/USER/backup.HOST/duplicity- inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg Handle 16 is a pipe: duplicity 28490 USER 16w FIFO 0,12 0t0 1415081 pipe Its other end is handle 13, I think: duplicity 28490 USER 13r FIFO 0,12 0t0 1415081 pipe But I do not see anyone reading from it. That sounds like the issue. It seems to be stuck in GIO file handling code: (gdb) bt #0 0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26 #1 0x7f0e6ee2672e in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #2 0x7f0e6ee2d827 in g_file_copy () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #3 0x7f0e76ccfdae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #4 0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #5 0x7f0e6fb8ecfa in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #6 0x7f0e6fb908e8 in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #7 0x7f0e6fb84c39 in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #8 0x5560917a1f60 in PyEval_EvalFrameEx () I have already tried to restart it and it got stuck like this again the next backup cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1778638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778638] Re: duplicity stuck in splice() call on Bionic
** Changed in: duplicity Importance: Medium => Undecided -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1778638 Title: duplicity stuck in splice() call on Bionic Status in Duplicity: Incomplete Status in deja-dup package in Ubuntu: Triaged Bug description: I am using Duplicity through Deja-Dup through its deja-dup-monitor process. After update to Bionic, it has basically stopped doing backups. Version is duplicity 0.7.17+bzr1357, Python version is 2.7.15rc1, Xubuntu Bionic. It seems to be stuck in pipes related call. When I try to strace the process I get this: strace: Process 28490 attached splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE From handle 9 to 16. The handle 9 is a file on my CIFS mount to where I do backups. If I go to the directory and do ls it works fine: duplicity 28490 USER9r REG 0,52 359 67128742 /var/backups/USER/backup.HOST/duplicity- inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg Handle 16 is a pipe: duplicity 28490 USER 16w FIFO 0,12 0t0 1415081 pipe Its other end is handle 13, I think: duplicity 28490 USER 13r FIFO 0,12 0t0 1415081 pipe But I do not see anyone reading from it. That sounds like the issue. It seems to be stuck in GIO file handling code: (gdb) bt #0 0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26 #1 0x7f0e6ee2672e in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #2 0x7f0e6ee2d827 in g_file_copy () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #3 0x7f0e76ccfdae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #4 0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #5 0x7f0e6fb8ecfa in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #6 0x7f0e6fb908e8 in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #7 0x7f0e6fb84c39 in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #8 0x5560917a1f60 in PyEval_EvalFrameEx () I have already tried to restart it and it got stuck like this again the next backup cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1778638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 676042] Update bug:, status confirmed, importance medium
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 status confirmed importance medium done -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmHRQACgkQH1G0ZBEH M/E/AAf+MZaZWPdkBWLx6pZV/wxe6uj8ONurmdDQokXiXWyCflydf9gJxCUX1FKb M51L4nlApghWR9uYf5lX0JYb8oaSsspIu8JMz5IS/7l29MeGS6b0wt0shPmQM6fY c2gcLdq9cbuLGw98ZonZf8Q2hCfYjtBI4SL2VxWSXZ3mcEWY4YP140iv053DmLnp BFtdQpgFX+1V5a7TC5B8UwzQ+i6eW7B7OIUM2J4KJrVcqdp9AOsYkWXKfiNVVCjj 0cB3PE4jsk/S+Q4DvJJR4A8FE7uJnfZGv0r01ugC0JMcxbRqOsOnv3VfNHKpPvCT PwsSlp9CfJKLto64SymqJU3SWIUTWw== =CdqP -END PGP SIGNATURE- ** Changed in: duplicity Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/676042 Title: duplicity falsely reports succeeded backup, empty manifest file Status in Duplicity: Confirmed Status in duplicity package in Ubuntu: New Bug description: duplicity version duplicity 0.6.09 Python 2.5.2 Distributor ID: Debian Description: Debian GNU/Linux 5.0.6 (lenny) Release: 5.0.6 Codename: lenny ==backup log snip== ionice -c 3 nice -n 9 duplicity incremental --full-if-older-than 2W --asynchronous-upload --no-encryption --asynchronous-upload --no-encryption --exclude '/tmp/**' --exclude '/proc/**' --exclude '/dev/**' --exclude '/sys/**' --exclude '/root/.cache/**' --exclude '/var/cache/duplicity/**' --exclude '/var/marsnet/duplicity/**' --exclude '/var/alternc/mnt/**' --exclude '/var/lib/mysql/**' --exclude '/var/alternc/db/**' --exclude '/var/log/mysql/**' / ssh://backup@mybckhost//opt/marsnet/backups/ Local and Remote metadata are synchronized, no sync needed. Last full backup date: Thu Oct 28 01:13:25 2010 Last full backup is too old, forcing full backup --[ Backup Statistics ]-- StartTime 1289607215.28 (Sat Nov 13 01:13:35 2010) EndTime 1289636885.88 (Sat Nov 13 09:28:05 2010) ElapsedTime 29670.59 (8 hours 14 minutes 30.59 seconds) SourceFiles 1730868 SourceFileSize 106161258939 (98.9 GB) NewFiles 1730868 NewFileSize 106161244989 (98.9 GB) DeletedFiles 0 ChangedFiles 0 ChangedFileSize 0 (0 bytes) ChangedDeltaSize 0 (0 bytes) DeltaEntries 1730868 RawDeltaSize 105419449446 (98.2 GB) TotalDestinationSizeChange 65491887291 (61.0 GB) Errors 0 - ++ hostname --fqdn + ionice -c 3 nice -n 9 duplicity remove-all-but-n-full 1 --force --no-encryption ssh://backup@mybckhost//opt/marsnet/backups/ Local and Remote metadata are synchronized, no sync needed. Last full backup date: Sat Nov 13 01:13:30 2010 Deleting backup set at time: Thu Oct 28 01:13:25 2010 Deleting this file from backend: duplicity-full-signatures.20101027T231325Z.sigtar.gz ==end snip== This is the log from the backup that failed. Ihave conditional execution so backups aren't removed if duplicity fails. In this case there was no error, but I found an empty manifest file in the destination directory. Sorry, i don't use extra verbose output in my backup scripts. All the restore scripts fail silently: they see the archive as empty, this could be the reason why duplicity reported success on exit? (very annoying, i just had to restore a file, i'm trying to recover at least a part of it using simple gunzip and tar..) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/676042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 918489] Re: duplicity allows a new, different passphrase if an archive cache exists
** Changed in: duplicity Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows a new, different passphrase if an archive cache exists Status in Déjà Dup: Fix Released Status in Duplicity: Fix Released Status in deja-dup package in Ubuntu: Fix Released Status in duplicity package in Ubuntu: Triaged Status in deja-dup source package in Trusty: Fix Released Status in duplicity source package in Trusty: Confirmed Status in deja-dup source package in Xenial: Fix Released Status in duplicity source package in Xenial: Confirmed Status in deja-dup source package in Yakkety: Fix Released Status in duplicity source package in Yakkety: Confirmed Bug description: when doing a backup for the first time, dejadup verifies your passphrase by having you enter it twice. on future incremental backups it doesn't need to do this because entering the wrong password will result in the backup failing. with the periodic 'full' backups that happen from time to time, however, any password will be accepted. this can lead to a situation where you accidentally type the wrong password once and are left in a situation where you don't know what you typed and have no way to get your files (or do another incremental backup on top of it). i think this is what happened to me recently. clearly, the fix is to explicitly verify the passphrase is correct when doing a new full backup. this may be a duplicity bug. === Ubuntu deja-dup SRU information === [impact] Users may unwittingly re-set their backup password and not be able to restore their data. [test case] - $ deja-dup-preferences # set up a dummy backup - $ deja-dup --backup # complete first encrypted full backup - $ rename 's/\.2016/\.2000/' /path/to/test/backup/* - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/* - $ deja-dup --backup # second backup, enter the wrong password - $ deja-dup --restore # try to restore with original password [regression potential] Should be limited? The fix is to delete the duplicity cache files, which ought to be safe to delete. It's possible if a full backup is being resumed, we might delete the current progress. That is a better bug to have than this bug, though. A more complicated patch would need to be investigated to prevent that. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1576051] Update bug #1576051, status confirmed, importance medium
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 status confirmed importance medium done -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmFfMACgkQH1G0ZBEH M/FnDQgAhImWqh76T9WUH4NzzfarEEZsdLKXg6lspkK14v3nEV0J1kd4PnsgxmL0 k0c2q3vcUOuB0QTyydWb5Jzf4C6JzmIRZEkJaHNojU7oFgyzu+AFq3r56/UdVFh/ yw84Ly3vaxN25BlR+T5kHENHtzmp9sMS8KdcECwh7EfxtxluItF/bkXk8kYukhlO WhnEkiyw/Fb6+5sQ0tl73t+V9zLOn2WrTLpSxaAsiZMel33aOBYgoPOic0v+Wpsv B407MFxAen5Z4EKHWwpQ2HLHik6OXiir6ZVX400+6inSJflqBCobJM0Lm/NH8OKu NacHNc7wXXHVGI9vKMliwg36OTJvCg== =/NIB -END PGP SIGNATURE- ** Changed in: duplicity Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1576051 Title: Duplicity cannot handle sparse files efficiently Status in Duplicity: Confirmed Status in duplicity package in Ubuntu: Confirmed Bug description: When running backup with duplicity, it cannot handle sparse files efficiently. I have a virtual machine image on my home dir, 26G -rw-r--r-- 1 libvirt-qemu kvm 33G huhti 28 08:59 dev02.img And duplicity is backing it up 33G, when it should only back up 26G. Steps to reproduce 1. Use qemu-image to create a sparse file 2. Run duplicity 3. Observe duplicity back it up whole instead of very small size To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1576051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652410] Update bug #1652410, status confirmed, importance medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
status confirmed
importance medium
done
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmFc0ACgkQH1G0ZBEH
M/GUCwgAoXIyBDb6kUITjvrIJVhKO8CXv/94R1PxitsoYebTWK1D8TUkOWFmy+mS
2NFM/IsMk5XbIrMgPvaJCyp/CuGzehzIV6hBaQVyhOg9VcuAKSNJ4bSNeABmXqrM
dh7GoiuY7ECn6gybCUznONyDvMJXbhR6/hqZgfOqDZGeNHNMtFpa+72qgcdpnuQh
+ymv+CO9ZyVMqv2Zuh53U53AuBpB9O3NWKhTbYTB3uS8C546jvAzfUEApuSFVYS8
yerauyOPF+BoX6Kcvv2zT52exvrVjTFD6Nmrr3W1SItGP8ayg0lVgdgez3UDaZ/0
W0Euv6sOx6i5LUFmPkgVoJ9pfw6VbQ==
=HUg5
-END PGP SIGNATURE-
** Changed in: duplicity
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
Undescriptive duplicity/collection-status error when the backup
directory contains two volumes with different file names and same
volume number in the same backup set
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
[System]
Ubuntu 16.04
deja-dup 34.2-0ubuntu1.1
duplicity 0.7.06-2ubuntu2
[Symptoms]
When the backup location unfortunately contains two backup volumes
with different file names and same volume number in the same backup
set, for instance:
duplicity-full.20161129T015237Z.vol1.difftar
duplicity-full.20161129T015237Z.vol1.difftar.gz
this confuses duplicity collection-status, which ends up returning an
undescriptive Python assertion error, as seen in this Déjà-Dup log
file:
DUPLICITY: INFO 1
DUPLICITY: . Args: /usr/bin/duplicity collection-status [...]
[...]
DUPLICITY: DEBUG 1
DUPLICITY: . 12 files exist on backend
DUPLICITY: DEBUG 1
DUPLICITY: . Extracting backup chains from list of files:
[u'duplicity-full.20161129T015237Z.vol1.difftar',
u'duplicity-full.20161129T015237Z.manifest',
u'duplicity-full.20161129T015237Z.vol1.difftar.gz',
u'duplicity-full-signatures.20161129T015237Z.sigtar.gz',
u'duplicity-full-signatures.20161129T015237Z.sigtar',
[...]
DUPLICITY: DEBUG 1
DUPLICITY: . File duplicity-full.20161129T015237Z.vol1.difftar is not
part of a known set; creating new set
DUPLICITY: DEBUG 1
DUPLICITY: . File duplicity-full.20161129T015237Z.manifest is part of
known set
DUPLICITY: ERROR 30 AssertionError
[...]
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/collections.
py", line 105, in add_filename(self.volume_name_dict, filename)
DUPLICITY: . AssertionError:
({1: 'duplicity-full.20161129T015237Z.vol1.difftar'},
'duplicity-full.20161129T015237Z.vol1.difftar.gz')
What happens is that duplicity collection-status takes the
uncompressed duplicity-full.20161129T015237Z.vol1.difftar for the
start of a backup set, then tries to add the compressed duplicity-
full.20161129T015237Z.vol1.difftar.gz to this set, and fails because
the volume number of this file has already been added to the set.
Otherwise there would be two backup volumes with the same volume
number in the backup set.
Note that a similar issue may also happen for file signatures instead
of backup volumes, e.g.:
duplicity-full-signatures.20161129T015237Z.sigtar
duplicity-full-signatures.20161129T015237Z.sigtar.gz
but backup volumes appear to be tripped on first, perhaps because of
alphabetic order.
Note also that under normal operation, the backup location isn't
supposed to contain a mixed of compressed and uncompressed files (or
encrypted and unencrypted files), but this situation was still
reported by the bug reporter in the original bug report.
[Test case]
See comment 19, written for Déjà-Dup, but easily adaptable to pure
duplicity I think.
[Ideas for fixing]
Duplicity already has checks to avoid considering files whose names
don't look like they could be part of a backup set (see comment 19,
point 4). Perhaps this filename filter could be improved on so that
duplicity doesn't burp so hard when a backup volume is present in both
compressed and uncompressed forms? Perhaps it could have duplicity
prefer a particular filename when there are two volumes with the same
number in the same backup set? But then which one and on what grounds?
Please also see comment 23.
[Easier fix]
Worst case, if this situation can't be handled automatically and the
situation requires a human to examine the contents of the backup
repository to take adequate action, then it would be helpful that
duplicity return a more descriptive message than the current terse
assertion error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1652410/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-pa
[Desktop-packages] [Bug 1788150] Re: Shebang should point to Python 2
** Changed in: duplicity Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1788150 Title: Shebang should point to Python 2 Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Released Bug description: I think we should change the shebang line to ensure Python 2 usage, as I have 3 set as default. This will produce and error as the statvfs package is deprecated, but available, in 2 and removed in 3. The error this produces in Deja Dup is "could not understgand duplicity version". To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1788150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 629357] Re: [Feature Request] support xz for compressing volumes
** Changed in: duplicity Status: Opinion => New ** Changed in: duplicity Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/629357 Title: [Feature Request] support xz for compressing volumes Status in Duplicity: New Status in duplicity package in Ubuntu: Opinion Bug description: xz offers a superior compression ratio at the cost of higher CPU load during creation of backup, but still decompresses (when you need it most) at a rapid pace. I don't know if it should be the default but adding it as an option could save yottabytes of bandwidth :) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/629357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878560] Re: Restore fails with “too many open files”
** Changed in: duplicity Status: Opinion => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1878560 Title: Restore fails with “too many open files” Status in Duplicity: Invalid Status in duplicity package in Ubuntu: New Bug description: I use duplicity with Backblaze B2, have an incremental backup every hour and a full backup every 90 days. I recently tried to restore a file to the state that it had 14 days ago. Eventually it failed saying “too many open files”. Apparently the last full backup was 2020-03-08 15:00:05Z. So that means that _a lot_ of incremental backups needed to be resolved. These are the last lines of output: Get: duplicity-inc.20200414T190005Z.to.20200414T25Z.vol1.difftar.gpg -> temp/duplicity-a7n2sb9u-tempdir/mktemp-619jt1ub-252 Verarbeitung des lokalen Manifest b'/home/mu/.cache/duplicity/17532b308f659397a23dae3345234484/duplicity-inc.20200414T25Z.to.20200414T210005Z.manifest' (7297) 1 Volumen in Manifest gefunden Get: duplicity-inc.20200414T25Z.to.20200414T210005Z.vol1.difftar.gpg -> temp/duplicity-a7n2sb9u-tempdir/mktemp-z7996evy-253 Verarbeitung des lokalen Manifest b'/home/mu/.cache/duplicity/17532b308f659397a23dae3345234484/duplicity-inc.20200414T210005Z.to.20200414T220005Z.manifest' (5983) 1 Volumen in Manifest gefunden Get: duplicity-inc.20200414T210005Z.to.20200414T220005Z.vol1.difftar.gpg -> temp/duplicity-a7n2sb9u-tempdir/mktemp-alqkws80-254 Traceback (innermost last): File "/usr/bin/duplicity", line 100, in with_tempdir(main) File "/usr/bin/duplicity", line 86, in with_tempdir fn() File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 1538, in main do_backup(action) File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 1618, in do_backup restore(col_stats) File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 723, in restore if not patchdir.Write_ROPaths(globals.local_path, File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 578, in Write_ROPaths for ropath in rop_iter: File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 541, in integrate_patch_iters for patch_seq in collated: File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 407, in yield_tuples setrorps(overflow, elems) File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 396, in setrorps elems[i] = next(iter_list[i]) File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 126, in difftar2path_iter tarinfo_list = [next(tar_iter)] File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 355, in __next__ self.set_tarfile() File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 348, in set_tarfile self.current_fp = next(self.fileobj_iter) File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 759, in get_fileobj_iter yield restore_get_enc_fileobj(backup_set.backend, File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 804, in restore_get_enc_fileobj fileobj = tdp.filtered_open_with_delete(u"rb") File "/usr/lib64/python3.8/site-packages/duplicity/dup_temp.py", line 125, in filtered_open_with_delete fh = FileobjHooked(path.DupPath.filtered_open(self, mode)) File "/usr/lib64/python3.8/site-packages/duplicity/path.py", line 802, in filtered_open return gpg.GPGFile(False, self, gpg_profile) File "/usr/lib64/python3.8/site-packages/duplicity/gpg.py", line 225, in __init__ p1 = gnupg.run([u'--decrypt'], create_fhs=gnupg_fhs, File "/usr/lib64/python3.8/site-packages/duplicity/gpginterface.py", line 374, in run process = self._attach_fork_exec(gnupg_commands, args, File "/usr/lib64/python3.8/site-packages/duplicity/gpginterface.py", line 403, in _attach_fork_exec pipe = os.pipe() OSError: [Errno 24] Too many open files I would assume that it stumbles over the 1024 file descriptor limit and it just cannot resolve a backup with that many incremental backups. Basically with the current state of the software my incremental backups are worthless because I cannot restore. Is there something that I can do except doing less frequent incremental updates and more full backups? To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1878560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity
Status: Confirmed => Incomplete
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
** Changed in: duplicity
Importance: High => Undecided
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
Status in Duplicity:
Incomplete
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
For 4 days déjà dup hasn't been able to perform a backup. It fails
with the error
Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
0x3d503338L',), )
There is another similar bug #676767 where deleting ~/.cache/deja-dup
helps. In this case it doesn't.
I'm quite certain that my backup drive isn't corrupted. (It's a
raid5.) I'd be happy to provide any additional information needed.
--
System information:
Ubuntu 11.10
deja-dup 20.0-0ubuntu3
duplicity 0.6.15-0ubuntu2
Logs:
deja-dup.log: http://pastie.org/2705320
deja-dup.gsettings: http://pastie.org/2705322
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1177381] Re: Duplicity can't find its own tempdir
** Changed in: duplicity
Status: In Progress => Fix Released
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1177381
Title:
Duplicity can't find its own tempdir
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
My backups have been working normally for months, but today they
failed with this error:
Failed with an unknown error:
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1411, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1404, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1386, in main
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 581, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 394, in write_multivol
vi.set_hash("SHA1", gpg.get_hash("SHA1", tdp))
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 401, in
get_hash
fp = path.open("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 542, in open
result = open(self.name, mode)
IOError: [Errno 2] No such file or directory:
'/tmp/duplicity-rWgqMw-tempdir/mktemp-fvN6e5-5'
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: deja-dup 26.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Tue May 7 09:12:25 2013
InstallationDate: Installed on 2010-09-17 (962 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: deja-dup
UpgradeStatus: Upgraded to raring on 2013-01-25 (101 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1177381/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727653] Re: error: can't start new thread
** Changed in: duplicity
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1727653
Title:
error: can't start new thread
Status in Duplicity:
Fix Released
Status in deja-dup package in Ubuntu:
Triaged
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731631] Re: KeyError: 56
** Changed in: duplicity Status: In Progress => New ** Changed in: duplicity Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned) ** Changed in: duplicity Importance: Medium => Undecided -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1731631 Title: KeyError: 56 Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Last run of Deja-dup has ended up with the following error: Traceback (innermost last): File "/usr/bin/duplicity", line 1559, in with_tempdir(main) File "/usr/bin/duplicity", line 1545, in with_tempdir fn() File "/usr/bin/duplicity", line 1394, in main do_backup(action) File "/usr/bin/duplicity", line 1473, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 729, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 765, in get_fileobj_iter backup_set.volume_name_dict[vol_num], KeyError: 56 This is with 0.7.14+bzr1336-0ubuntu3~ubuntu17.10.1. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1731631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778638] Re: duplicity stuck in splice() call on Bionic
** Changed in: duplicity Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1778638 Title: duplicity stuck in splice() call on Bionic Status in Duplicity: Incomplete Status in deja-dup package in Ubuntu: Triaged Bug description: I am using Duplicity through Deja-Dup through its deja-dup-monitor process. After update to Bionic, it has basically stopped doing backups. Version is duplicity 0.7.17+bzr1357, Python version is 2.7.15rc1, Xubuntu Bionic. It seems to be stuck in pipes related call. When I try to strace the process I get this: strace: Process 28490 attached splice(9, [359], 16, NULL, 1048576, SPLICE_F_MORE From handle 9 to 16. The handle 9 is a file on my CIFS mount to where I do backups. If I go to the directory and do ls it works fine: duplicity 28490 USER9r REG 0,52 359 67128742 /var/backups/USER/backup.HOST/duplicity- inc.20180611T014226Z.to.20180612T014125Z.manifest.gpg Handle 16 is a pipe: duplicity 28490 USER 16w FIFO 0,12 0t0 1415081 pipe Its other end is handle 13, I think: duplicity 28490 USER 13r FIFO 0,12 0t0 1415081 pipe But I do not see anyone reading from it. That sounds like the issue. It seems to be stuck in GIO file handling code: (gdb) bt #0 0x7f0e78588dda in splice (fd_in=9, off_in=0x7ffe5e958388, fd_out=16, off_out=0x0, len=1048576, flags=4) at ../sysdeps/unix/sysv/linux/splice.c:26 #1 0x7f0e6ee2672e in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #2 0x7f0e6ee2d827 in g_file_copy () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #3 0x7f0e76ccfdae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #4 0x7f0e76ccf71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #5 0x7f0e6fb8ecfa in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #6 0x7f0e6fb908e8 in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #7 0x7f0e6fb84c39 in () at /usr/lib/python2.7/dist-packages/gi/_gi.x86_64-linux-gnu.so #8 0x5560917a1f60 in PyEval_EvalFrameEx () I have already tried to restart it and it got stuck like this again the next backup cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1778638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878560] Re: Restore fails with “too many open files”
** Changed in: duplicity Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1878560 Title: Restore fails with “too many open files” Status in Duplicity: Opinion Status in duplicity package in Ubuntu: New Bug description: I use duplicity with Backblaze B2, have an incremental backup every hour and a full backup every 90 days. I recently tried to restore a file to the state that it had 14 days ago. Eventually it failed saying “too many open files”. Apparently the last full backup was 2020-03-08 15:00:05Z. So that means that _a lot_ of incremental backups needed to be resolved. These are the last lines of output: Get: duplicity-inc.20200414T190005Z.to.20200414T25Z.vol1.difftar.gpg -> temp/duplicity-a7n2sb9u-tempdir/mktemp-619jt1ub-252 Verarbeitung des lokalen Manifest b'/home/mu/.cache/duplicity/17532b308f659397a23dae3345234484/duplicity-inc.20200414T25Z.to.20200414T210005Z.manifest' (7297) 1 Volumen in Manifest gefunden Get: duplicity-inc.20200414T25Z.to.20200414T210005Z.vol1.difftar.gpg -> temp/duplicity-a7n2sb9u-tempdir/mktemp-z7996evy-253 Verarbeitung des lokalen Manifest b'/home/mu/.cache/duplicity/17532b308f659397a23dae3345234484/duplicity-inc.20200414T210005Z.to.20200414T220005Z.manifest' (5983) 1 Volumen in Manifest gefunden Get: duplicity-inc.20200414T210005Z.to.20200414T220005Z.vol1.difftar.gpg -> temp/duplicity-a7n2sb9u-tempdir/mktemp-alqkws80-254 Traceback (innermost last): File "/usr/bin/duplicity", line 100, in with_tempdir(main) File "/usr/bin/duplicity", line 86, in with_tempdir fn() File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 1538, in main do_backup(action) File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 1618, in do_backup restore(col_stats) File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 723, in restore if not patchdir.Write_ROPaths(globals.local_path, File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 578, in Write_ROPaths for ropath in rop_iter: File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 541, in integrate_patch_iters for patch_seq in collated: File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 407, in yield_tuples setrorps(overflow, elems) File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 396, in setrorps elems[i] = next(iter_list[i]) File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 126, in difftar2path_iter tarinfo_list = [next(tar_iter)] File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 355, in __next__ self.set_tarfile() File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 348, in set_tarfile self.current_fp = next(self.fileobj_iter) File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 759, in get_fileobj_iter yield restore_get_enc_fileobj(backup_set.backend, File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 804, in restore_get_enc_fileobj fileobj = tdp.filtered_open_with_delete(u"rb") File "/usr/lib64/python3.8/site-packages/duplicity/dup_temp.py", line 125, in filtered_open_with_delete fh = FileobjHooked(path.DupPath.filtered_open(self, mode)) File "/usr/lib64/python3.8/site-packages/duplicity/path.py", line 802, in filtered_open return gpg.GPGFile(False, self, gpg_profile) File "/usr/lib64/python3.8/site-packages/duplicity/gpg.py", line 225, in __init__ p1 = gnupg.run([u'--decrypt'], create_fhs=gnupg_fhs, File "/usr/lib64/python3.8/site-packages/duplicity/gpginterface.py", line 374, in run process = self._attach_fork_exec(gnupg_commands, args, File "/usr/lib64/python3.8/site-packages/duplicity/gpginterface.py", line 403, in _attach_fork_exec pipe = os.pipe() OSError: [Errno 24] Too many open files I would assume that it stumbles over the 1024 file descriptor limit and it just cannot resolve a backup with that many incremental backups. Basically with the current state of the software my incremental backups are worthless because I cannot restore. Is there something that I can do except doing less frequent incremental updates and more full backups? To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1878560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1919017] Re: MultiBackend incorrectly reporting a failure on file deletion
** Changed in: duplicity
Milestone: None => 0.8.19
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1919017
Title:
MultiBackend incorrectly reporting a failure on file deletion
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
New
Bug description:
Steps to reproduce:
- create multi.json file with the following contents
[
{
"description": "dstA",
"url": "file:///tmp/dstA"
},
{
"description": "dstB",
"url": "file:///tmp/dstB"
}
]
# Make 10 full backups of /etc/hosts
for i in $(seq 10)
do
/usr/bin/duplicity --no-encryption full /etc/hosts
'multi:///path/to/multi.json?mode=mirror'
sleep 1
done
# listing the contents of destinationA
$ ls -1 /tmp/dstA
duplicity-full-signatures.20210313T100123Z.sigtar.gz
duplicity-full-signatures.20210313T100152Z.sigtar.gz
duplicity-full-signatures.20210313T100154Z.sigtar.gz
duplicity-full-signatures.20210313T100155Z.sigtar.gz
duplicity-full-signatures.20210313T100156Z.sigtar.gz
duplicity-full-signatures.20210313T100158Z.sigtar.gz
duplicity-full-signatures.20210313T100159Z.sigtar.gz
duplicity-full-signatures.20210313T100200Z.sigtar.gz
duplicity-full-signatures.20210313T100202Z.sigtar.gz
duplicity-full-signatures.20210313T100203Z.sigtar.gz
duplicity-full-signatures.20210313T100205Z.sigtar.gz
duplicity-full.20210313T100123Z.manifest
duplicity-full.20210313T100123Z.vol1.difftar.gz
duplicity-full.20210313T100152Z.manifest
duplicity-full.20210313T100152Z.vol1.difftar.gz
duplicity-full.20210313T100154Z.manifest
duplicity-full.20210313T100154Z.vol1.difftar.gz
duplicity-full.20210313T100155Z.manifest
duplicity-full.20210313T100155Z.vol1.difftar.gz
duplicity-full.20210313T100156Z.manifest
duplicity-full.20210313T100156Z.vol1.difftar.gz
duplicity-full.20210313T100158Z.manifest
duplicity-full.20210313T100158Z.vol1.difftar.gz
duplicity-full.20210313T100159Z.manifest
duplicity-full.20210313T100159Z.vol1.difftar.gz
duplicity-full.20210313T100200Z.manifest
duplicity-full.20210313T100200Z.vol1.difftar.gz
duplicity-full.20210313T100202Z.manifest
duplicity-full.20210313T100202Z.vol1.difftar.gz
duplicity-full.20210313T100203Z.manifest
duplicity-full.20210313T100203Z.vol1.difftar.gz
duplicity-full.20210313T100205Z.manifest
duplicity-full.20210313T100205Z.vol1.difftar.gz
# issue a request to delete all but 1 full backup
$ /usr/bin/duplicity --verbosity 9 --no-encryption remove-all-but-n-full 1
'multi:///path/to/multi.json?mode=mirror' --force 2>&1 | grep 'failed to delete'
MultiBackend: failed to delete
b'duplicity-full-signatures.20210313T100203Z.sigtar.gz' from file:///tmp/dstA
MultiBackend: failed to delete
b'duplicity-full-signatures.20210313T100203Z.sigtar.gz' from file:///tmp/dstB
MultiBackend: failed to delete
b'duplicity-full-signatures.20210313T100202Z.sigtar.gz' from file:///tmp/dstA
MultiBackend: failed to delete
b'duplicity-full-signatures.20210313T100202Z.sigtar.gz' from file:///tmp/dstB
..
$ ls -l /tmp/dstA/duplicity-full-signatures.20210313T100203Z.sigtar.gz
ls: cannot access
'/tmp/dstA/duplicity-full-signatures.20210313T100203Z.sigtar.gz': No such file
or directory
# failure is reported even despite the fact that the files were
correctly removed
The issue seems to be caused by the code starting at
https://git.launchpad.net/duplicity/tree/duplicity/backends/multibackend.py#n345
duplicity 0.8.18
python 3.9.2
Arch Linux, x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1919017/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1919017] Re: MultiBackend incorrectly reporting a failure on file deletion
** Also affects: ubuntu
Importance: Undecided
Status: New
** No longer affects: ubuntu
** Also affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1919017
Title:
MultiBackend incorrectly reporting a failure on file deletion
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
New
Bug description:
Steps to reproduce:
- create multi.json file with the following contents
[
{
"description": "dstA",
"url": "file:///tmp/dstA"
},
{
"description": "dstB",
"url": "file:///tmp/dstB"
}
]
# Make 10 full backups of /etc/hosts
for i in $(seq 10)
do
/usr/bin/duplicity --no-encryption full /etc/hosts
'multi:///path/to/multi.json?mode=mirror'
sleep 1
done
# listing the contents of destinationA
$ ls -1 /tmp/dstA
duplicity-full-signatures.20210313T100123Z.sigtar.gz
duplicity-full-signatures.20210313T100152Z.sigtar.gz
duplicity-full-signatures.20210313T100154Z.sigtar.gz
duplicity-full-signatures.20210313T100155Z.sigtar.gz
duplicity-full-signatures.20210313T100156Z.sigtar.gz
duplicity-full-signatures.20210313T100158Z.sigtar.gz
duplicity-full-signatures.20210313T100159Z.sigtar.gz
duplicity-full-signatures.20210313T100200Z.sigtar.gz
duplicity-full-signatures.20210313T100202Z.sigtar.gz
duplicity-full-signatures.20210313T100203Z.sigtar.gz
duplicity-full-signatures.20210313T100205Z.sigtar.gz
duplicity-full.20210313T100123Z.manifest
duplicity-full.20210313T100123Z.vol1.difftar.gz
duplicity-full.20210313T100152Z.manifest
duplicity-full.20210313T100152Z.vol1.difftar.gz
duplicity-full.20210313T100154Z.manifest
duplicity-full.20210313T100154Z.vol1.difftar.gz
duplicity-full.20210313T100155Z.manifest
duplicity-full.20210313T100155Z.vol1.difftar.gz
duplicity-full.20210313T100156Z.manifest
duplicity-full.20210313T100156Z.vol1.difftar.gz
duplicity-full.20210313T100158Z.manifest
duplicity-full.20210313T100158Z.vol1.difftar.gz
duplicity-full.20210313T100159Z.manifest
duplicity-full.20210313T100159Z.vol1.difftar.gz
duplicity-full.20210313T100200Z.manifest
duplicity-full.20210313T100200Z.vol1.difftar.gz
duplicity-full.20210313T100202Z.manifest
duplicity-full.20210313T100202Z.vol1.difftar.gz
duplicity-full.20210313T100203Z.manifest
duplicity-full.20210313T100203Z.vol1.difftar.gz
duplicity-full.20210313T100205Z.manifest
duplicity-full.20210313T100205Z.vol1.difftar.gz
# issue a request to delete all but 1 full backup
$ /usr/bin/duplicity --verbosity 9 --no-encryption remove-all-but-n-full 1
'multi:///path/to/multi.json?mode=mirror' --force 2>&1 | grep 'failed to delete'
MultiBackend: failed to delete
b'duplicity-full-signatures.20210313T100203Z.sigtar.gz' from file:///tmp/dstA
MultiBackend: failed to delete
b'duplicity-full-signatures.20210313T100203Z.sigtar.gz' from file:///tmp/dstB
MultiBackend: failed to delete
b'duplicity-full-signatures.20210313T100202Z.sigtar.gz' from file:///tmp/dstA
MultiBackend: failed to delete
b'duplicity-full-signatures.20210313T100202Z.sigtar.gz' from file:///tmp/dstB
..
$ ls -l /tmp/dstA/duplicity-full-signatures.20210313T100203Z.sigtar.gz
ls: cannot access
'/tmp/dstA/duplicity-full-signatures.20210313T100203Z.sigtar.gz': No such file
or directory
# failure is reported even despite the fact that the files were
correctly removed
The issue seems to be caused by the code starting at
https://git.launchpad.net/duplicity/tree/duplicity/backends/multibackend.py#n345
duplicity 0.8.18
python 3.9.2
Arch Linux, x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1919017/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
Snarky and off topic, but true.
I've left this bug open intentionally since it happens on occasion. I
don't believe duplicity is at fault. Mostly these kind of errors happen
because of:
-- Ctrl-C happy users and Python's poor handling of signals.
-- Consumer grade electronics with: memory without ECC or parity,
routers that have packet confirmation turned off, the occasional hard
drive bit rot, or any other factor that makes equipment cheap to buy.
Errors are rare but in a high population it's a lot less rare than you
might imagine.
So, please take your spam and leave it where it belongs, in the bit
bucket.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
For 4 days déjà dup hasn't been able to perform a backup. It fails
with the error
Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
0x3d503338L',), )
There is another similar bug #676767 where deleting ~/.cache/deja-dup
helps. In this case it doesn't.
I'm quite certain that my backup drive isn't corrupted. (It's a
raid5.) I'd be happy to provide any additional information needed.
--
System information:
Ubuntu 11.10
deja-dup 20.0-0ubuntu3
duplicity 0.6.15-0ubuntu2
Logs:
deja-dup.log: http://pastie.org/2705320
deja-dup.gsettings: http://pastie.org/2705322
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908971] Re: TypeError: cannot use a string pattern on a bytes-like object
Your report got truncated somehow... I need the traceback as well as the error message. I think this has been fixed in a later version, we're at 0.8.17 now. Please try an upgrade if possible There are multiple options both stable and daily: - Source - https://gitlab.com/duplicity/duplicity - Stable tarball install - https://launchpad.net/duplicity/+download - Stable duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-release-git - Daily duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-develop-git - Stable snap builds - “sudo snap install duplicity —classic" - Latest snap builds - “sudo snap install duplicity —classic —edge" - Stable pip3 builds - “sudo pip3 install duplicity" - Latest pip3 builds - “sudo pip3 install --pre duplicity" Note 1: UNINSTALL duplicity first if it was installed from a different source.. This is due to divergent install locations, especially between repository installs and the other forms. Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10, Focal 20.04, and Hirsute 20.10. Xenial 16.04 works with Snap and Pip installs, but cannot be built under Launchpad PPAs at the moment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1908971 Title: TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: New Bug description: user@host:~$ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.11.1612-1 Candidate: 0.8.11.1612-1 Version table: *** 0.8.11.1612-1 500 500 http://nz.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status user@host:~$ http_proxy= AWS_ACCESS_KEY_ID=[omitted-key-id] AWS_SECRET_ACCESS_KEY=[omitted-key] PASSPHRASE=[omitted-encryption-password] duplicity --s3-use-new-style --s3-use-ia --s3-use-multiprocessing --no-print-statistics --verbosity 1 --exclude-device-files --exclude-filelist [omitted-exclude-path] --include-filelist [omitted-include-path] --exclude '**' / [omitted-s3-storage-path] TypeError: cannot use a string pattern on a bytes-like object During handling of the above exception, another exception occurred: Traceback (most recent call last): ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: duplicity 0.8.11.1612-1 ProcVersionSignature: Ubuntu 5.8.0-33.36-lowlatency 5.8.17 Uname: Linux 5.8.0-33-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Dec 22 16:37:45 2020 InstallationDate: Installed on 2020-11-19 (33 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1908971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908971] Re: TypeError: cannot use a string pattern on a bytes-like object
** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1908971 Title: TypeError: cannot use a string pattern on a bytes-like object Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: New Bug description: user@host:~$ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.11.1612-1 Candidate: 0.8.11.1612-1 Version table: *** 0.8.11.1612-1 500 500 http://nz.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status user@host:~$ http_proxy= AWS_ACCESS_KEY_ID=[omitted-key-id] AWS_SECRET_ACCESS_KEY=[omitted-key] PASSPHRASE=[omitted-encryption-password] duplicity --s3-use-new-style --s3-use-ia --s3-use-multiprocessing --no-print-statistics --verbosity 1 --exclude-device-files --exclude-filelist [omitted-exclude-path] --include-filelist [omitted-include-path] --exclude '**' / [omitted-s3-storage-path] TypeError: cannot use a string pattern on a bytes-like object During handling of the above exception, another exception occurred: Traceback (most recent call last): ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: duplicity 0.8.11.1612-1 ProcVersionSignature: Ubuntu 5.8.0-33.36-lowlatency 5.8.17 Uname: Linux 5.8.0-33-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Dec 22 16:37:45 2020 InstallationDate: Installed on 2020-11-19 (33 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1908971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904622] Re: boto3+s3 bucket fails
** Changed in: duplicity Importance: Medium => Undecided ** Changed in: duplicity Status: In Progress => Invalid ** Changed in: duplicity Milestone: 0.8.18 => None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1904622 Title: boto3+s3 bucket fails Status in Duplicity: Invalid Status in duplicity package in Ubuntu: Incomplete Bug description: I have a duplicity job that runs on multiple hosts, and am now having failures on my 20.04 hosts. The syntax for the job (as I am currently testing to debug) is: duplicity --dry-run list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Using the duplicity packages from focal/main duplicity=0.8.11.1612-1 And I installed the boto packages from focal/universe python3-boto3=1.9.253-1 python3-botocore=1.14.14+repack-1 This runs into the error: Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir Traceback (innermost last): File "/usr/bin/duplicity", line 106, in with_tempdir(main) File "/usr/bin/duplicity", line 92, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 96, in reset_connection self.s3.meta.client.head_bucket(Bucket=self.bucket_name) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call return self._make_api_call(operation_name, kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call raise error_class(parsed_response, operation_name) botocore.exceptions.ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I then tried the duplicity snap from the snap store, both the stable and edge builds, with the same issue: Main action: list-current duplicity 0.8.17 Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden Main action: list-current duplicity 0.8.18.dev11 Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I also tried to update the boto3/botocore packages by way of pip3: pip3 freeze | grep boto boto3==1.16.19 botocore==1.19.19 And lastly as a last ditch, I tried to pull the packages from the groovy/universe repo, bringing them to: python3-boto3 1.13.14-1 python3-botocore 1.17.22+repack-1_all I have also tried in a 20.10 system as well to see if any changes there, but same results. Hoping for something I can look at to get this back working as it was in 18.04 since 14.04. For good measure, I verified in a bionic build that using the same arguments as above with duplicity=0.7.17
[Desktop-packages] [Bug 1904622] Re: boto3+s3 bucket fails
Sorry, it took me a while to grok that you were using the boto3 backend. The format for a boto3 URL is boto3+s3://bucket_name[/prefix]. It's in the man page and usage screen. Make that change and let me know how it went. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1904622 Title: boto3+s3 bucket fails Status in Duplicity: In Progress Status in duplicity package in Ubuntu: Incomplete Bug description: I have a duplicity job that runs on multiple hosts, and am now having failures on my 20.04 hosts. The syntax for the job (as I am currently testing to debug) is: duplicity --dry-run list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Using the duplicity packages from focal/main duplicity=0.8.11.1612-1 And I installed the boto packages from focal/universe python3-boto3=1.9.253-1 python3-botocore=1.14.14+repack-1 This runs into the error: Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir Traceback (innermost last): File "/usr/bin/duplicity", line 106, in with_tempdir(main) File "/usr/bin/duplicity", line 92, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 96, in reset_connection self.s3.meta.client.head_bucket(Bucket=self.bucket_name) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call return self._make_api_call(operation_name, kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call raise error_class(parsed_response, operation_name) botocore.exceptions.ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I then tried the duplicity snap from the snap store, both the stable and edge builds, with the same issue: Main action: list-current duplicity 0.8.17 Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden Main action: list-current duplicity 0.8.18.dev11 Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I also tried to update the boto3/botocore packages by way of pip3: pip3 freeze | grep boto boto3==1.16.19 botocore==1.19.19 And lastly as a last ditch, I tried to pull the packages from the groovy/universe repo, bringing them to: python3-boto3 1.13.14-1 python3-botocore 1.17.22+repack-1_all I have also tried in a 20.10 system as well to see if any changes there, but same results. Hoping for something I can look at to get this back working as it was in 18.04 since 14.04. For good measure, I verified in a bionic build that using the
[Desktop-packages] [Bug 1904622] Re: boto3+s3 bucket fails
Thanks for the thorough analysis. ** Changed in: duplicity Importance: Undecided => Medium ** Changed in: duplicity Milestone: None => 0.8.18 ** Changed in: duplicity Status: Incomplete => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1904622 Title: boto3+s3 bucket fails Status in Duplicity: In Progress Status in duplicity package in Ubuntu: Incomplete Bug description: I have a duplicity job that runs on multiple hosts, and am now having failures on my 20.04 hosts. The syntax for the job (as I am currently testing to debug) is: duplicity --dry-run list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Using the duplicity packages from focal/main duplicity=0.8.11.1612-1 And I installed the boto packages from focal/universe python3-boto3=1.9.253-1 python3-botocore=1.14.14+repack-1 This runs into the error: Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir Traceback (innermost last): File "/usr/bin/duplicity", line 106, in with_tempdir(main) File "/usr/bin/duplicity", line 92, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 96, in reset_connection self.s3.meta.client.head_bucket(Bucket=self.bucket_name) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call return self._make_api_call(operation_name, kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call raise error_class(parsed_response, operation_name) botocore.exceptions.ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I then tried the duplicity snap from the snap store, both the stable and edge builds, with the same issue: Main action: list-current duplicity 0.8.17 Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden Main action: list-current duplicity 0.8.18.dev11 Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I also tried to update the boto3/botocore packages by way of pip3: pip3 freeze | grep boto boto3==1.16.19 botocore==1.19.19 And lastly as a last ditch, I tried to pull the packages from the groovy/universe repo, bringing them to: python3-boto3 1.13.14-1 python3-botocore 1.17.22+repack-1_all I have also tried in a 20.10 system as well to see if any changes there, but same results. Hoping for something I can look at to get this back working as it was in 18.04 since 14.04. For good measure, I verified in a bionic build that using the sam
[Desktop-packages] [Bug 1904622] Re: boto3+s3 bucket fails
Please upgrade to the current version of duplicity. This will assure that any bugs fixed since your release are available and may fix your issue. Current release is 0.8.17. I would suggest using one of the snap builds if at all possible. There are multiple options both stable and daily: - Source - https://gitlab.com/duplicity/duplicity - Stable tarball install - https://launchpad.net/duplicity/+download - Stable duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-release-git - Daily duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-develop-git - Stable snap builds - “sudo snap install duplicity —classic" - Latest snap builds - “sudo snap install duplicity —classic —edge" - Stable pip3 builds - “sudo pip3 install duplicity" - Latest pip3 builds - “sudo pip3 install --pre duplicity" Note 1: UNINSTALL duplicity first if it was installed from a different source.. This is due to divergent install locations, especially between repository installs and the other forms. Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10, Focal 20.04, and Hirsute 20.10. Xenial 16.04 works with Snap and Pip installs, but cannot be built under Launchpad PPAs at the moment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1904622 Title: boto3+s3 bucket fails Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: Incomplete Bug description: I have a duplicity job that runs on multiple hosts, and am now having failures on my 20.04 hosts. The syntax for the job (as I am currently testing to debug) is: duplicity --dry-run list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Using the duplicity packages from focal/main duplicity=0.8.11.1612-1 And I installed the boto packages from focal/universe python3-boto3=1.9.253-1 python3-botocore=1.14.14+repack-1 This runs into the error: Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir Traceback (innermost last): File "/usr/bin/duplicity", line 106, in with_tempdir(main) File "/usr/bin/duplicity", line 92, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 96, in reset_connection self.s3.meta.client.head_bucket(Bucket=self.bucket_name) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call return self._make_api_call(operation_name, kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call raise error_class(parsed_response, operation_name) botocore.exceptions.ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I then tried the duplicity snap from the snap store, both the stable and edge builds, with the same issue: Main action: list-current duplicity 0.8.17 Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden Main action: list-current duplicity 0.8.18.dev11 Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosit
[Desktop-packages] [Bug 1904622] Re: boto3+s3 bucket fails
Have you tried reading your files with s3cmd or another tool? If that works, check permission keys etc.. If that does not work, I'd like a log file, please. This is going big and I only need a portion. Please run with -v9, redirect to a log file, then run: $ head -n 200 < log > log.head $ tail -n 200 < log > log.tail Attach, do NOT copy/paste, log.head and log.tail to this bug report. See green button below. ** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1904622 Title: boto3+s3 bucket fails Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: New Bug description: I have a duplicity job that runs on multiple hosts, and am now having failures on my 20.04 hosts. The syntax for the job (as I am currently testing to debug) is: duplicity --dry-run list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Using the duplicity packages from focal/main duplicity=0.8.11.1612-1 And I installed the boto packages from focal/universe python3-boto3=1.9.253-1 python3-botocore=1.14.14+repack-1 This runs into the error: Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir Traceback (innermost last): File "/usr/bin/duplicity", line 106, in with_tempdir(main) File "/usr/bin/duplicity", line 92, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 96, in reset_connection self.s3.meta.client.head_bucket(Bucket=self.bucket_name) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call return self._make_api_call(operation_name, kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call raise error_class(parsed_response, operation_name) botocore.exceptions.ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I then tried the duplicity snap from the snap store, both the stable and edge builds, with the same issue: Main action: list-current duplicity 0.8.17 Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden Main action: list-current duplicity 0.8.18.dev11 Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I also tried to update the boto3/botocore packages by way of pip3: pip3 freeze | grep boto boto3==1.16.19 botocore==1.19.19 And lastly as a last ditch, I tried to pull the packages from the groovy/universe repo, bringing them to: python3-boto3 1.13.14-1 p
[Desktop-packages] [Bug 1893481] Re: UnicodeEncodeError when logging improperly encoded filenames
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1893481
Title:
UnicodeEncodeError when logging improperly encoded filenames
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
Fix Committed
Bug description:
Attempts to log messages which contain unicode surrogate characters cause
exceptions.
(These surrogate characters arise, for example, when handling files whose
names are not properly encoded as UTF-8.)
NOTE: I have no idea whether this is an issue when running on python
2. (If it is, the fixes suggested below probably won't work.)
Duplicity version: 0.8.15
Python version: 3.8.5
Target filesystem: Linux
Example log output:
--- Logging error ---
Traceback (most recent call last):
File "/opt/Python-3.8.5/lib/python3.8/logging/__init__.py", line 1084, in
emit
stream.write(msg + self.terminator)
UnicodeEncodeError: 'utf-8' codec can't encode character '\udcc4' in position
45: surrogates not allowed
Call stack:
File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 104, in
with_tempdir(main)
File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 90, in
with_tempdir
fn()
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 1531, in main
do_backup(action)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 1655, in do_backup
full_backup(col_stats)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 559, in full_backup
bytes_written = write_multivol(u"full", tarblock_iter,
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 417, in write_multivol
at_end = gpg.GPGWriteFile(tarblock_iter, tdp.name, config.gpg_profile,
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/gpg.py",
line 390, in GPGWriteFile
data = block_iter.__next__().data
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 544, in __next__
result = self.process(next(self.input_iter)) # pylint:
disable=assignment-from-no-return
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 238, in get_delta_iter
log_delta_path(delta_path, new_path, stats)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 181, in log_delta_path
log.Info(_(u"A %s") %
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py",
line 128, in Info
Log(s, INFO, code, extra)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py",
line 91, in Log
_logger.log(DupToLoggerLevel(verb_level), s,
Message: 'A home/dairiki/PRCS/junk-changelog/22_Senaste\udcc4nd,v'
Arguments: ()
Steps to reproduce:
- Have a file with funny characters in its name, encoded in latin-1 encoding.
E.g. a file whose name is "Fü" encoded to latin-1 (b'F\xfc'). When duplicity
handles this file, the improperly encoded character will be replaced with a
unicode surrogate character.
- Attempt to create an archive containing this file, with verbosity set to 5.
Duplicity will try to log each file processed. When it gets to this file, an
exception will be reported (and the file will not make it into the archive.)
Alternative steps to produce:
- If the archive is created with verbosity less than 5, the file will make it
into the archive. However, if an attempt is made to list files using
'duplicity list-current-files', an exception will be reported when it gets to
the file with the funny name.
Workaround
==
A simple workaround is to set the environment variable
PYTHONIOENCODING="utf-8:surrogateescape" before running duplicity.
This will set the encoding error mode for stdout and stderr to
'surrogateescape' (by default it is 'strict') with the effect that any
surrogates will be replaced with the unicode replacement character
(U+FFFD: "�").
Possible Fix
A possible fix, at least for Py3K, is probably for duplicity to explicitly
set the encoding error strategy for stdin and stdout.
For python >= 3.7 this is simple:
sys.stdin.reconfigure(errors='surrogateescape')
sys.stderr.reconfigure(errors='surrogateescape')
For earlier pythons (>= 3), the best option might be:
sys.stdin = codecs.getwriter('utf-8')(sys.stdin.detach(),
'surrogateescape')
(and similarly for stderr)
Note that python 2 doesn't know about errors='surrogateescape'.
Errors='replace' would probably work as an alternative, but it's not
ideal as it replaces
[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start
First, this is not the same bug, but a support issue. duplicity can't stat /home/nikodll/.hardinfo/.deja-dup-ignore, so you need to run duplicity as root, i.e. 'sudo duplicity ...'. Thanks! I needed something simple today! :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Bug description: I am on 19.10. Duplicity crashes as soon as I try to start a backup, as below. It was running fine on 19.04. Traceback (innermost last): File "/usr/bin/duplicity", line 107, in with_tempdir(main) File "/usr/bin/duplicity", line 93, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 81, in __init__ ensure_dbus() File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", line 37, in ensure_dbus lines = output.split(u'\n') TypeError: a bytes-like object is required, not 'str' To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893481] Re: UnicodeEncodeError when logging improperly encoded filenames
** Changed in: duplicity Status: Confirmed => Fix Committed ** Changed in: duplicity Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1893481 Title: UnicodeEncodeError when logging improperly encoded filenames Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: New Bug description: Attempts to log messages which contain unicode surrogate characters cause exceptions. (These surrogate characters arise, for example, when handling files whose names are not properly encoded as UTF-8.) NOTE: I have no idea whether this is an issue when running on python 2. (If it is, the fixes suggested below probably won't work.) Duplicity version: 0.8.15 Python version: 3.8.5 Target filesystem: Linux Example log output: --- Logging error --- Traceback (most recent call last): File "/opt/Python-3.8.5/lib/python3.8/logging/__init__.py", line 1084, in emit stream.write(msg + self.terminator) UnicodeEncodeError: 'utf-8' codec can't encode character '\udcc4' in position 45: surrogates not allowed Call stack: File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 104, in with_tempdir(main) File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 90, in with_tempdir fn() File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py", line 1531, in main do_backup(action) File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py", line 1655, in do_backup full_backup(col_stats) File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py", line 559, in full_backup bytes_written = write_multivol(u"full", tarblock_iter, File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py", line 417, in write_multivol at_end = gpg.GPGWriteFile(tarblock_iter, tdp.name, config.gpg_profile, File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/gpg.py", line 390, in GPGWriteFile data = block_iter.__next__().data File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py", line 544, in __next__ result = self.process(next(self.input_iter)) # pylint: disable=assignment-from-no-return File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py", line 238, in get_delta_iter log_delta_path(delta_path, new_path, stats) File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py", line 181, in log_delta_path log.Info(_(u"A %s") % File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py", line 128, in Info Log(s, INFO, code, extra) File "/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py", line 91, in Log _logger.log(DupToLoggerLevel(verb_level), s, Message: 'A home/dairiki/PRCS/junk-changelog/22_Senaste\udcc4nd,v' Arguments: () Steps to reproduce: - Have a file with funny characters in its name, encoded in latin-1 encoding. E.g. a file whose name is "Fü" encoded to latin-1 (b'F\xfc'). When duplicity handles this file, the improperly encoded character will be replaced with a unicode surrogate character. - Attempt to create an archive containing this file, with verbosity set to 5. Duplicity will try to log each file processed. When it gets to this file, an exception will be reported (and the file will not make it into the archive.) Alternative steps to produce: - If the archive is created with verbosity less than 5, the file will make it into the archive. However, if an attempt is made to list files using 'duplicity list-current-files', an exception will be reported when it gets to the file with the funny name. Workaround == A simple workaround is to set the environment variable PYTHONIOENCODING="utf-8:surrogateescape" before running duplicity. This will set the encoding error mode for stdout and stderr to 'surrogateescape' (by default it is 'strict') with the effect that any surrogates will be replaced with the unicode replacement character (U+FFFD: "�"). Possible Fix A possible fix, at least for Py3K, is probably for duplicity to explicitly set the encoding error strategy for stdin and stdout. For python >= 3.7 this is simple: sys.stdin.reconfigure(errors='surrogateescape') sys.stderr.reconfi
[Desktop-packages] [Bug 1893481] Re: UnicodeEncodeError when logging improperly encoded filenames
Please run locale from a terminal and copy/paste the result in a
comment.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1893481
Title:
UnicodeEncodeError when logging improperly encoded filenames
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
New
Bug description:
Attempts to log messages which contain unicode surrogate characters cause
exceptions.
(These surrogate characters arise, for example, when handling files whose
names are not properly encoded as UTF-8.)
NOTE: I have no idea whether this is an issue when running on python
2. (If it is, the fixes suggested below probably won't work.)
Duplicity version: 0.8.15
Python version: 3.8.5
Target filesystem: Linux
Example log output:
--- Logging error ---
Traceback (most recent call last):
File "/opt/Python-3.8.5/lib/python3.8/logging/__init__.py", line 1084, in
emit
stream.write(msg + self.terminator)
UnicodeEncodeError: 'utf-8' codec can't encode character '\udcc4' in position
45: surrogates not allowed
Call stack:
File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 104, in
with_tempdir(main)
File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 90, in
with_tempdir
fn()
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 1531, in main
do_backup(action)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 1655, in do_backup
full_backup(col_stats)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 559, in full_backup
bytes_written = write_multivol(u"full", tarblock_iter,
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 417, in write_multivol
at_end = gpg.GPGWriteFile(tarblock_iter, tdp.name, config.gpg_profile,
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/gpg.py",
line 390, in GPGWriteFile
data = block_iter.__next__().data
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 544, in __next__
result = self.process(next(self.input_iter)) # pylint:
disable=assignment-from-no-return
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 238, in get_delta_iter
log_delta_path(delta_path, new_path, stats)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 181, in log_delta_path
log.Info(_(u"A %s") %
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py",
line 128, in Info
Log(s, INFO, code, extra)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py",
line 91, in Log
_logger.log(DupToLoggerLevel(verb_level), s,
Message: 'A home/dairiki/PRCS/junk-changelog/22_Senaste\udcc4nd,v'
Arguments: ()
Steps to reproduce:
- Have a file with funny characters in its name, encoded in latin-1 encoding.
E.g. a file whose name is "Fü" encoded to latin-1 (b'F\xfc'). When duplicity
handles this file, the improperly encoded character will be replaced with a
unicode surrogate character.
- Attempt to create an archive containing this file, with verbosity set to 5.
Duplicity will try to log each file processed. When it gets to this file, an
exception will be reported (and the file will not make it into the archive.)
Alternative steps to produce:
- If the archive is created with verbosity less than 5, the file will make it
into the archive. However, if an attempt is made to list files using
'duplicity list-current-files', an exception will be reported when it gets to
the file with the funny name.
Workaround
==
A simple workaround is to set the environment variable
PYTHONIOENCODING="utf-8:surrogateescape" before running duplicity.
This will set the encoding error mode for stdout and stderr to
'surrogateescape' (by default it is 'strict') with the effect that any
surrogates will be replaced with the unicode replacement character
(U+FFFD: "�").
Possible Fix
A possible fix, at least for Py3K, is probably for duplicity to explicitly
set the encoding error strategy for stdin and stdout.
For python >= 3.7 this is simple:
sys.stdin.reconfigure(errors='surrogateescape')
sys.stderr.reconfigure(errors='surrogateescape')
For earlier pythons (>= 3), the best option might be:
sys.stdin = codecs.getwriter('utf-8')(sys.stdin.detach(),
'surrogateescape')
(and similarly for stderr)
Note that python 2 doesn't know about errors='surrogateescape'.
Errors='replace' would probably work as an alternative, but it's not
ideal as it replaces the surr
[Desktop-packages] [Bug 1893481] Re: UnicodeEncodeError when logging improperly encoded filenames
** Also affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1893481
Title:
UnicodeEncodeError when logging improperly encoded filenames
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
New
Bug description:
Attempts to log messages which contain unicode surrogate characters cause
exceptions.
(These surrogate characters arise, for example, when handling files whose
names are not properly encoded as UTF-8.)
NOTE: I have no idea whether this is an issue when running on python
2. (If it is, the fixes suggested below probably won't work.)
Duplicity version: 0.8.15
Python version: 3.8.5
Target filesystem: Linux
Example log output:
--- Logging error ---
Traceback (most recent call last):
File "/opt/Python-3.8.5/lib/python3.8/logging/__init__.py", line 1084, in
emit
stream.write(msg + self.terminator)
UnicodeEncodeError: 'utf-8' codec can't encode character '\udcc4' in position
45: surrogates not allowed
Call stack:
File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 104, in
with_tempdir(main)
File "/root/.local/pipx/venvs/duplicity/bin/duplicity", line 90, in
with_tempdir
fn()
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 1531, in main
do_backup(action)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 1655, in do_backup
full_backup(col_stats)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 559, in full_backup
bytes_written = write_multivol(u"full", tarblock_iter,
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/dup_main.py",
line 417, in write_multivol
at_end = gpg.GPGWriteFile(tarblock_iter, tdp.name, config.gpg_profile,
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/gpg.py",
line 390, in GPGWriteFile
data = block_iter.__next__().data
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 544, in __next__
result = self.process(next(self.input_iter)) # pylint:
disable=assignment-from-no-return
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 238, in get_delta_iter
log_delta_path(delta_path, new_path, stats)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/diffdir.py",
line 181, in log_delta_path
log.Info(_(u"A %s") %
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py",
line 128, in Info
Log(s, INFO, code, extra)
File
"/root/.local/pipx/venvs/duplicity/lib/python3.8/site-packages/duplicity/log.py",
line 91, in Log
_logger.log(DupToLoggerLevel(verb_level), s,
Message: 'A home/dairiki/PRCS/junk-changelog/22_Senaste\udcc4nd,v'
Arguments: ()
Steps to reproduce:
- Have a file with funny characters in its name, encoded in latin-1 encoding.
E.g. a file whose name is "Fü" encoded to latin-1 (b'F\xfc'). When duplicity
handles this file, the improperly encoded character will be replaced with a
unicode surrogate character.
- Attempt to create an archive containing this file, with verbosity set to 5.
Duplicity will try to log each file processed. When it gets to this file, an
exception will be reported (and the file will not make it into the archive.)
Alternative steps to produce:
- If the archive is created with verbosity less than 5, the file will make it
into the archive. However, if an attempt is made to list files using
'duplicity list-current-files', an exception will be reported when it gets to
the file with the funny name.
Workaround
==
A simple workaround is to set the environment variable
PYTHONIOENCODING="utf-8:surrogateescape" before running duplicity.
This will set the encoding error mode for stdout and stderr to
'surrogateescape' (by default it is 'strict') with the effect that any
surrogates will be replaced with the unicode replacement character
(U+FFFD: "�").
Possible Fix
A possible fix, at least for Py3K, is probably for duplicity to explicitly
set the encoding error strategy for stdin and stdout.
For python >= 3.7 this is simple:
sys.stdin.reconfigure(errors='surrogateescape')
sys.stderr.reconfigure(errors='surrogateescape')
For earlier pythons (>= 3), the best option might be:
sys.stdin = codecs.getwriter('utf-8')(sys.stdin.detach(),
'surrogateescape')
(and similarly for stderr)
Note that python 2 doesn't know about errors='surrogateescape'.
Errors='replace' would probably work as an alternative, but it's not
ideal as it replaces th
[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
It has been a long while since this occurred, except when restoring from
an older backup. What produced the zeroes is beyond my guess. Very
weird.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
Status in Duplicity:
Confirmed
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
For 4 days déjà dup hasn't been able to perform a backup. It fails
with the error
Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
0x3d503338L',), )
There is another similar bug #676767 where deleting ~/.cache/deja-dup
helps. In this case it doesn't.
I'm quite certain that my backup drive isn't corrupted. (It's a
raid5.) I'd be happy to provide any additional information needed.
--
System information:
Ubuntu 11.10
deja-dup 20.0-0ubuntu3
duplicity 0.6.15-0ubuntu2
Logs:
deja-dup.log: http://pastie.org/2705320
deja-dup.gsettings: http://pastie.org/2705322
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889152] Re: Introduction of detailed S3 parameters breaks existing AWS setups
** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1889152 Title: Introduction of detailed S3 parameters breaks existing AWS setups Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Bug description: Hi, I just got an update of duplicity via snap to version 0.8.15. Running my backup script running duplicity as follows: ``` duplicity incremental --include-filelist backup_include.lst.txt \ --exclude-filelist backup_exclude.lst.txt \ --exclude-other-filesystems \ --exclude-device-files \ --progress \ --full-if-older-than 45D \ $HOME \ boto3+s3:/// ``` ...resulted in the following error: ``` Traceback (innermost last): File "/snap/duplicity/111/bin/duplicity", line 104, in with_tempdir(main) File "/snap/duplicity/111/bin/duplicity", line 90, in with_tempdir fn() File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/dup_main.py", line 1518, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine backup, local_pathname = set_backend(args[0], args[1]) File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/commandline.py", line 1071, in set_backend config.backend = backend.get_backend(bend) File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backend.py", line 223, in get_backend obj = get_backend_object(url_string) File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backend.py", line 209, in get_backend_object return factory(pu) File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backends/s3_boto3_backend.py", line 93, in reset_connection self.s3 = boto3.resource(u's3', region_name=config.s3_region_name, endpoint_url=config.s3_endpoint_url) AttributeError: module 'duplicity.config' has no attribute 's3_region_name' ``` *Actual behaviour* It seems like the changes introduced via https://gitlab.com/duplicity/duplicity/-/merge_requests/19 made the parameters `s3-region-name` and `s3-endpoint-url` mandatory, which breaks existing AWS S3 setups. *Expected behaviour* These parameters should be optional. *Duplicity version*: 0.8.15 *Python version*: 3.6 *OS distro and version*: Ubuntu 20.04 *Target filesystem*: Linux to AWS S3 Thanks for your work! EDIT: Added duplicity command. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1889152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875937] Re: Download of vol1 in validate_encryption_settings() fails when using S3 glacier
It seems to be working as it should. When you do the incremental are you specifying the storage class or using IA? We check to see if --s3 -use-deep-archive or --s3-use-glacier is used and don't run validate_encryption_settings() if either is set. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1875937 Title: Download of vol1 in validate_encryption_settings() fails when using S3 glacier Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Bug description: Duplicity version: 0.8.12.1612 ubuntu 20.04 LTS python 3.8.2 When i try to restart a backup which goes to S3 (via boto3) (use of: --s3-use-deep-archive or --s3-use-glacier) it fails: Last full backup date: Wed Apr 29 17:45:32 2020 RESTART: Volumes 2 to 2 failed to upload before termination. Restarting backup at volume 2. Attempt 1 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class Attempt 2 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class This is because a file stored in glacier cannot be downloaded. I dont know if this known? To solve this: either skip validate_encryption_settings() when using any of this storage backends or introduce an option to skip the download manually (e.g. --skip-download-on-restart) I fixed it for me with manully skipping the validate_encryption_settings() function. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1875937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889152] Re: Introduction of detailed S3 parameters breaks existing AWS setups
** Also affects: duplicity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1889152 Title: Introduction of detailed S3 parameters breaks existing AWS setups Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: New Bug description: Hi, I just got an update of duplicity via snap to version 0.8.15. Running my backup script running duplicity as follows: ``` duplicity incremental --include-filelist backup_include.lst.txt \ --exclude-filelist backup_exclude.lst.txt \ --exclude-other-filesystems \ --exclude-device-files \ --progress \ --full-if-older-than 45D \ $HOME \ boto3+s3:/// ``` ...resulted in the following error: ``` Traceback (innermost last): File "/snap/duplicity/111/bin/duplicity", line 104, in with_tempdir(main) File "/snap/duplicity/111/bin/duplicity", line 90, in with_tempdir fn() File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/dup_main.py", line 1518, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/commandline.py", line 1200, in ProcessCommandLine backup, local_pathname = set_backend(args[0], args[1]) File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/commandline.py", line 1071, in set_backend config.backend = backend.get_backend(bend) File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backend.py", line 223, in get_backend obj = get_backend_object(url_string) File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backend.py", line 209, in get_backend_object return factory(pu) File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backends/s3_boto3_backend.py", line 93, in reset_connection self.s3 = boto3.resource(u's3', region_name=config.s3_region_name, endpoint_url=config.s3_endpoint_url) AttributeError: module 'duplicity.config' has no attribute 's3_region_name' ``` *Actual behaviour* It seems like the changes introduced via https://gitlab.com/duplicity/duplicity/-/merge_requests/19 made the parameters `s3-region-name` and `s3-endpoint-url` mandatory, which breaks existing AWS S3 setups. *Expected behaviour* These parameters should be optional. *Duplicity version*: 0.8.15 *Python version*: 3.6 *OS distro and version*: Ubuntu 20.04 *Target filesystem*: Linux to AWS S3 Thanks for your work! EDIT: Added duplicity command. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1889152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875937] Re: Download of vol1 in validate_encryption_settings() fails when using S3 glacier
** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1875937 Title: Download of vol1 in validate_encryption_settings() fails when using S3 glacier Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Bug description: Duplicity version: 0.8.12.1612 ubuntu 20.04 LTS python 3.8.2 When i try to restart a backup which goes to S3 (via boto3) (use of: --s3-use-deep-archive or --s3-use-glacier) it fails: Last full backup date: Wed Apr 29 17:45:32 2020 RESTART: Volumes 2 to 2 failed to upload before termination. Restarting backup at volume 2. Attempt 1 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class Attempt 2 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class This is because a file stored in glacier cannot be downloaded. I dont know if this known? To solve this: either skip validate_encryption_settings() when using any of this storage backends or introduce an option to skip the download manually (e.g. --skip-download-on-restart) I fixed it for me with manully skipping the validate_encryption_settings() function. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1875937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881926] Re: deja-dup fails with root account
Yes, it was in bug #1851167. Linking the reports would have been
difficult.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1881926
Title:
deja-dup fails with root account
Status in Duplicity:
Invalid
Status in duplicity package in Ubuntu:
Fix Committed
Bug description:
I am running deja-dup in Ubuntu 20.04 (Focal Fossa), which has
duplicity/focal,now 0.8.11.1612-1 and deja-dup/focal,now
40.6-1ubuntu2.
When I run deja-dup as myself, it runs fine, but when I launch it with
sudo, it fails:
Traceback (innermost last):
File "/usr/bin/duplicity", line 106, in
with_tempdir(main)
File "/usr/bin/duplicity", line 92, in with_tempdir
fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in
main
action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175,
in ProcessCommandLine
globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in
get_backend
obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in
get_backend_object
return factory(pu)
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py",
line 82, in __init__
ensure_dbus()
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py",
line 37, in ensure_dbus
output = p.communicate()[0].decode("utf8", errors="replace")
AttributeError: 'str' object has no attribute 'decode'
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1881926/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881926] Re: deja-dup fails with root account
That bug has been fixed in 0.8.13. Please upgrade to the current
version of duplicity. This will assure that any bugs fixed since your
release are available and may fix your issue.
There are multiple options both stable and daily:
* Source - https://gitlab.com/duplicity/duplicity
* Stable tarball install - https://launchpad.net/duplicity/+download
* Daily duplicity PPA -
https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-develop-git
* Stable duplicity PPA -
https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-release-git
* Stable snap builds - “sudo snap install duplicity —classic"
* Latest snap builds - “sudo snap install duplicity —classic —edge"
* Latest pip3 builds - “sudo pip3 install duplicity"
NOTE: UNinstall duplicity first if it was installed via the distribution
repository. For Ubuntu that would be "sudo apt-get purge duplicity".
** Also affects: duplicity
Importance: Undecided
Status: New
** Changed in: duplicity
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1881926
Title:
deja-dup fails with root account
Status in Duplicity:
Invalid
Status in duplicity package in Ubuntu:
New
Bug description:
I am running deja-dup in Ubuntu 20.04 (Focal Fossa), which has
duplicity/focal,now 0.8.11.1612-1 and deja-dup/focal,now
40.6-1ubuntu2.
When I run deja-dup as myself, it runs fine, but when I launch it with
sudo, it fails:
Traceback (innermost last):
File "/usr/bin/duplicity", line 106, in
with_tempdir(main)
File "/usr/bin/duplicity", line 92, in with_tempdir
fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in
main
action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175,
in ProcessCommandLine
globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in
get_backend
obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in
get_backend_object
return factory(pu)
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py",
line 82, in __init__
ensure_dbus()
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py",
line 37, in ensure_dbus
output = p.communicate()[0].decode("utf8", errors="replace")
AttributeError: 'str' object has no attribute 'decode'
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1881926/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875937] Re: Download of vol1 in validate_encryption_settings() fails when using S3 glacier
** Changed in: duplicity Status: Triaged => Fix Committed ** Changed in: duplicity Milestone: None => 0.8.14 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1875937 Title: Download of vol1 in validate_encryption_settings() fails when using S3 glacier Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: New Bug description: Duplicity version: 0.8.12.1612 ubuntu 20.04 LTS python 3.8.2 When i try to restart a backup which goes to S3 (via boto3) (use of: --s3-use-deep-archive or --s3-use-glacier) it fails: Last full backup date: Wed Apr 29 17:45:32 2020 RESTART: Volumes 2 to 2 failed to upload before termination. Restarting backup at volume 2. Attempt 1 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class Attempt 2 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class This is because a file stored in glacier cannot be downloaded. I dont know if this known? To solve this: either skip validate_encryption_settings() when using any of this storage backends or introduce an option to skip the download manually (e.g. --skip-download-on-restart) I fixed it for me with manully skipping the validate_encryption_settings() function. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1875937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875937] Re: Download of vol1 in validate_encryption_settings() fails when using S3 glacier
When using boto3, glacier restore is not supported yet. You'll need to download the backup to a local drive and restore from there. ** Changed in: duplicity Status: New => Triaged ** Changed in: duplicity Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1875937 Title: Download of vol1 in validate_encryption_settings() fails when using S3 glacier Status in Duplicity: Triaged Status in duplicity package in Ubuntu: New Bug description: Duplicity version: 0.8.12.1612 ubuntu 20.04 LTS python 3.8.2 When i try to restart a backup which goes to S3 (via boto3) (use of: --s3-use-deep-archive or --s3-use-glacier) it fails: Last full backup date: Wed Apr 29 17:45:32 2020 RESTART: Volumes 2 to 2 failed to upload before termination. Restarting backup at volume 2. Attempt 1 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class Attempt 2 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class This is because a file stored in glacier cannot be downloaded. I dont know if this known? To solve this: either skip validate_encryption_settings() when using any of this storage backends or introduce an option to skip the download manually (e.g. --skip-download-on-restart) I fixed it for me with manully skipping the validate_encryption_settings() function. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1875937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878560] Re: Restore fails with “too many open files”
This is a known issue with duplicity. You will need to increase your systems number of open files since it's set so low. I'd suggest 16384 or higher if you have a lot of incrementals. I'd also suggest limiting the number of incrementals and doing more full backups. ** Also affects: duplicity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1878560 Title: Restore fails with “too many open files” Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: I use duplicity with Backblaze B2, have an incremental backup every hour and a full backup every 90 days. I recently tried to restore a file to the state that it had 14 days ago. Eventually it failed saying “too many open files”. Apparently the last full backup was 2020-03-08 15:00:05Z. So that means that _a lot_ of incremental backups needed to be resolved. These are the last lines of output: Get: duplicity-inc.20200414T190005Z.to.20200414T25Z.vol1.difftar.gpg -> temp/duplicity-a7n2sb9u-tempdir/mktemp-619jt1ub-252 Verarbeitung des lokalen Manifest b'/home/mu/.cache/duplicity/17532b308f659397a23dae3345234484/duplicity-inc.20200414T25Z.to.20200414T210005Z.manifest' (7297) 1 Volumen in Manifest gefunden Get: duplicity-inc.20200414T25Z.to.20200414T210005Z.vol1.difftar.gpg -> temp/duplicity-a7n2sb9u-tempdir/mktemp-z7996evy-253 Verarbeitung des lokalen Manifest b'/home/mu/.cache/duplicity/17532b308f659397a23dae3345234484/duplicity-inc.20200414T210005Z.to.20200414T220005Z.manifest' (5983) 1 Volumen in Manifest gefunden Get: duplicity-inc.20200414T210005Z.to.20200414T220005Z.vol1.difftar.gpg -> temp/duplicity-a7n2sb9u-tempdir/mktemp-alqkws80-254 Traceback (innermost last): File "/usr/bin/duplicity", line 100, in with_tempdir(main) File "/usr/bin/duplicity", line 86, in with_tempdir fn() File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 1538, in main do_backup(action) File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 1618, in do_backup restore(col_stats) File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 723, in restore if not patchdir.Write_ROPaths(globals.local_path, File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 578, in Write_ROPaths for ropath in rop_iter: File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 541, in integrate_patch_iters for patch_seq in collated: File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 407, in yield_tuples setrorps(overflow, elems) File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 396, in setrorps elems[i] = next(iter_list[i]) File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 126, in difftar2path_iter tarinfo_list = [next(tar_iter)] File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 355, in __next__ self.set_tarfile() File "/usr/lib64/python3.8/site-packages/duplicity/patchdir.py", line 348, in set_tarfile self.current_fp = next(self.fileobj_iter) File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 759, in get_fileobj_iter yield restore_get_enc_fileobj(backup_set.backend, File "/usr/lib64/python3.8/site-packages/duplicity/dup_main.py", line 804, in restore_get_enc_fileobj fileobj = tdp.filtered_open_with_delete(u"rb") File "/usr/lib64/python3.8/site-packages/duplicity/dup_temp.py", line 125, in filtered_open_with_delete fh = FileobjHooked(path.DupPath.filtered_open(self, mode)) File "/usr/lib64/python3.8/site-packages/duplicity/path.py", line 802, in filtered_open return gpg.GPGFile(False, self, gpg_profile) File "/usr/lib64/python3.8/site-packages/duplicity/gpg.py", line 225, in __init__ p1 = gnupg.run([u'--decrypt'], create_fhs=gnupg_fhs, File "/usr/lib64/python3.8/site-packages/duplicity/gpginterface.py", line 374, in run process = self._attach_fork_exec(gnupg_commands, args, File "/usr/lib64/python3.8/site-packages/duplicity/gpginterface.py", line 403, in _attach_fork_exec pipe = os.pipe() OSError: [Errno 24] Too many open files I would assume that it stumbles over the 1024 file descriptor limit and it just cannot resolve a backup with that many incremental backups. Basically with the current state of the software my incremental backups are worthless because I cannot restore. Is there something that I can do except doing less frequent incremental updates and more full backups? To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1878560/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-pack
[Desktop-packages] [Bug 1828761] Re: Incremental backups do not validate passphrase
** Also affects: duplicity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1828761 Title: Incremental backups do not validate passphrase Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: This was reported in a comment on another bug, but I think this is serious enough to warrant its own one. It broke my incremental backups and I just happened to notice. The report with repro steps is https://bugs.launchpad.net/duplicity/+bug/918489/comments/22 The expected behavior would be to fail on invalid passphrases on incremental backups (or otherwise make it very clear that this is the user's responsibility). I seem to remember testing this in the past and verifying that an error is raised. Right now, it leads to corruption and a beautiful stack trace followed by a hanging application when trying to verify or restore: GPG error detail: Traceback (innermost last): File "/bin/duplicity", line 1560, in with_tempdir(main) File "/bin/duplicity", line 1546, in with_tempdir fn() File "/bin/duplicity", line 1398, in main do_backup(action) File "/bin/duplicity", line 1479, in do_backup verify(col_stats) File "/bin/duplicity", line 875, in verify for backup_ropath, current_path in collated: File "/usr/lib/python2.7/site-packages/duplicity/diffdir.py", line 276, in collate2iters relem1 = riter1.next() File "/usr/lib/python2.7/site-packages/duplicity/patchdir.py", line 521, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/site-packages/duplicity/diffdir.py", line 286, in collate2iters relem2 = riter2.next() File "/usr/lib/python2.7/site-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/site-packages/duplicity/patchdir.py", line 344, in next self.set_tarfile() File "/usr/lib/python2.7/site-packages/duplicity/patchdir.py", line 332, in set_tarfile assert not self.current_fp.close() File "/usr/lib/python2.7/site-packages/duplicity/dup_temp.py", line 227, in close assert not self.fileobj.close() File "/usr/lib/python2.7/site-packages/duplicity/gpg.py", line 305, in close self.gpg_failed() File "/usr/lib/python2.7/site-packages/duplicity/gpg.py", line 272, in gpg_failed raise GPGError(msg) GPGError: GPG Failed, see log below: = Begin GnuPG log = gpg: AES encrypted data gpg: encrypted with 1 passphrase gpg: decryption failed: Bad session key = End GnuPG log = GPGError: GPG Failed, see log below: = Begin GnuPG log = gpg: AES encrypted data gpg: encrypted with 1 passphrase gpg: decryption failed: Bad session key = End GnuPG log = If left unnoticed, the only way to go about it is manual recovery. I'm updating my backup scripts to do some basic validation of the passphrase to make sure that a simple typo will not break my backups in the future. duplicity 0.7.18.2 on Arch Linux, Python 3.7.3. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1828761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876446] Re: WebDAV backend creates only tiny or 0 Byte files
** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1876446 Title: WebDAV backend creates only tiny or 0 Byte files Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Triaged Bug description: When using the WebDAV backend only tiny or 0-Byte files get created at the WebDAV storage. Duplicity itself doesn't report any error, only the uploaded file size is too small. Duplicity version: 0.8.12.1596 Python version: 3.6.10 OS Distro and version: gentoo Type of target filesystem: Linux, Windows, other.: WebDAV I created a 1000 Byte testfile. The uploaded file sizes are way too small: ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T104649Z.vol1.difftar.gpg ... WebDAV data length: 78 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full-signatures.20200502T104649Z.sigtar.gpg ... WebDAV data length: 138 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T104649Z.manifest.gpg ... WebDAV data length: 129 WebDAV response status 201 with reason 'Created'. ... Verification of this backup fails. I made a small fix in duplicity/backends/webdavbackend.py (see attachment) Now everything works as expected: ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T105219Z.vol1.difftar.gpg ... WebDAV data length: 28794233 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full-signatures.20200502T105219Z.sigtar.gpg ... WebDAV data length: 169724 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T105219Z.manifest.gpg ... WebDAV data length: 1332 WebDAV response status 201 with reason 'Created'. ... Verification of this backup was successful. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1876446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876778] Re: MEGA.nz backend issues after "conversion" to Python 3 (patch attached)
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1876778
Title:
MEGA.nz backend issues after "conversion" to Python 3 (patch attached)
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
New
Bug description:
Hello, despite I have never written anything in Python, it looks like
the problem is some automatic code "conversion" to make this
"duplicity" backend work with Python 3, or a similar issue, if the
fundamental issue is another please ignore and stick to the facts
below, thank you.
After upgrading from Ubuntu 18.04 LTS to 20.04 LTS, my "duplicity"-based
backup to offsite MEGA.nz stopped working. This is what I was getting as a
result (output shown for a fresh new test backup):
"""
export BACKUP_SOURCE="/tmp"
export BACKUP_DESTINATION="mega://mega_usern...@example.com@mega.co.nz/Test_2"
# duplicity --full-if-older-than 30D ${BACKUP_SOURCE} ${BACKUP_DESTINATION}
mkdir: Test_2
megals: /Root/Test_2
Attempt 1 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 2 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 3 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 4 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Giving up after 5 attempts. TypeError: a bytes-like object is required, not
'str'
mkdir: Test_2
megals: /Root/Test_2
Attempt 1 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 2 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 3 failed. TypeError: a bytes-like object is required, not 'str'
"""
After some research found out some calls to Python were being given a
byte-like object instead of strings (str). So googled around and added
some ".decode()" calls at some points in which strings were expected
(some trial and error seeing all similar errors in the MEGA.nz backend
data flow. After doing so, the backend resumed working normally
(resulting patch against current "duplicity" package is attached). So
please make a good patch from the one attached as reference and please
make its way into the Ubuntu package ASAP (don't know if upstream
version is affected as well).
More details about my current system:
"""
# lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04
# apt-cache policy duplicity
duplicity:
Instalados: 0.8.11.1612-1
Candidato: 0.8.11.1612-1
Tabla de versión:
*** 0.8.11.1612-1 500
500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
"""
Hope you find this valuable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1876778/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875529] Re: Support hiding instead of deleting for Backblaze B2 backend
** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1875529 Title: Support hiding instead of deleting for Backblaze B2 backend Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Confirmed Bug description: There should be an option to change the B2 backend to hide instead of deleting files. This can be done by changing this line in B2Backend: self.bucket.delete_file_version(file_version_info.id_, file_version_info.file_name) to this: self.bucket.hide_file(file_version_info.file_name) You can probably also remove the `file_info` call and just use the `path + fsdecode(...)` result, but I don't know enough about the B2 API/duplicity to say that for sure. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1875529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875529] Re: Support hiding instead of deleting for Backblaze B2 backend
** Changed in: duplicity Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1875529 Title: Support hiding instead of deleting for Backblaze B2 backend Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Confirmed Bug description: There should be an option to change the B2 backend to hide instead of deleting files. This can be done by changing this line in B2Backend: self.bucket.delete_file_version(file_version_info.id_, file_version_info.file_name) to this: self.bucket.hide_file(file_version_info.file_name) You can probably also remove the `file_info` call and just use the `path + fsdecode(...)` result, but I don't know enough about the B2 API/duplicity to say that for sure. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1875529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876446] Re: WebDAV backend creates only tiny or 0 Byte files
** Changed in: duplicity Status: In Progress => Fix Committed ** Changed in: duplicity Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1876446 Title: WebDAV backend creates only tiny or 0 Byte files Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Triaged Bug description: When using the WebDAV backend only tiny or 0-Byte files get created at the WebDAV storage. Duplicity itself doesn't report any error, only the uploaded file size is too small. Duplicity version: 0.8.12.1596 Python version: 3.6.10 OS Distro and version: gentoo Type of target filesystem: Linux, Windows, other.: WebDAV I created a 1000 Byte testfile. The uploaded file sizes are way too small: ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T104649Z.vol1.difftar.gpg ... WebDAV data length: 78 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full-signatures.20200502T104649Z.sigtar.gpg ... WebDAV data length: 138 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T104649Z.manifest.gpg ... WebDAV data length: 129 WebDAV response status 201 with reason 'Created'. ... Verification of this backup fails. I made a small fix in duplicity/backends/webdavbackend.py (see attachment) Now everything works as expected: ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T105219Z.vol1.difftar.gpg ... WebDAV data length: 28794233 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full-signatures.20200502T105219Z.sigtar.gpg ... WebDAV data length: 169724 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T105219Z.manifest.gpg ... WebDAV data length: 1332 WebDAV response status 201 with reason 'Created'. ... Verification of this backup was successful. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1876446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876778] Re: MEGA.nz backend issues after "conversion" to Python 3 (patch attached)
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: New => Fix Committed
** Changed in: duplicity
Milestone: None => 0.8.13
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1876778
Title:
MEGA.nz backend issues after "conversion" to Python 3 (patch attached)
Status in Duplicity:
Fix Committed
Status in duplicity package in Ubuntu:
New
Bug description:
Hello, despite I have never written anything in Python, it looks like
the problem is some automatic code "conversion" to make this
"duplicity" backend work with Python 3, or a similar issue, if the
fundamental issue is another please ignore and stick to the facts
below, thank you.
After upgrading from Ubuntu 18.04 LTS to 20.04 LTS, my "duplicity"-based
backup to offsite MEGA.nz stopped working. This is what I was getting as a
result (output shown for a fresh new test backup):
"""
export BACKUP_SOURCE="/tmp"
export BACKUP_DESTINATION="mega://mega_usern...@example.com@mega.co.nz/Test_2"
# duplicity --full-if-older-than 30D ${BACKUP_SOURCE} ${BACKUP_DESTINATION}
mkdir: Test_2
megals: /Root/Test_2
Attempt 1 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 2 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 3 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 4 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Giving up after 5 attempts. TypeError: a bytes-like object is required, not
'str'
mkdir: Test_2
megals: /Root/Test_2
Attempt 1 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 2 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 3 failed. TypeError: a bytes-like object is required, not 'str'
"""
After some research found out some calls to Python were being given a
byte-like object instead of strings (str). So googled around and added
some ".decode()" calls at some points in which strings were expected
(some trial and error seeing all similar errors in the MEGA.nz backend
data flow. After doing so, the backend resumed working normally
(resulting patch against current "duplicity" package is attached). So
please make a good patch from the one attached as reference and please
make its way into the Ubuntu package ASAP (don't know if upstream
version is affected as well).
More details about my current system:
"""
# lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04
# apt-cache policy duplicity
duplicity:
Instalados: 0.8.11.1612-1
Candidato: 0.8.11.1612-1
Tabla de versión:
*** 0.8.11.1612-1 500
500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
"""
Hope you find this valuable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1876778/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875529] Re: Support hiding instead of deleting for Backblaze B2 backend
** Changed in: duplicity Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1875529 Title: Support hiding instead of deleting for Backblaze B2 backend Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: Confirmed Bug description: There should be an option to change the B2 backend to hide instead of deleting files. This can be done by changing this line in B2Backend: self.bucket.delete_file_version(file_version_info.id_, file_version_info.file_name) to this: self.bucket.hide_file(file_version_info.file_name) You can probably also remove the `file_info` call and just use the `path + fsdecode(...)` result, but I don't know enough about the B2 API/duplicity to say that for sure. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1875529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875529] Re: Support hiding instead of deleting for Backblaze B2 backend
** Also affects: duplicity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1875529 Title: Support hiding instead of deleting for Backblaze B2 backend Status in Duplicity: In Progress Status in duplicity package in Ubuntu: Confirmed Bug description: There should be an option to change the B2 backend to hide instead of deleting files. This can be done by changing this line in B2Backend: self.bucket.delete_file_version(file_version_info.id_, file_version_info.file_name) to this: self.bucket.hide_file(file_version_info.file_name) You can probably also remove the `file_info` call and just use the `path + fsdecode(...)` result, but I don't know enough about the B2 API/duplicity to say that for sure. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1875529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875937] Re: Download of vol1 in validate_encryption_settings() fails when using S3 glacier
** Also affects: ubuntu Importance: Undecided Status: New ** No longer affects: ubuntu ** Also affects: duplicity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1875937 Title: Download of vol1 in validate_encryption_settings() fails when using S3 glacier Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Duplicity version: 0.8.12.1612 ubuntu 20.04 LTS python 3.8.2 When i try to restart a backup which goes to S3 (via boto3) (use of: --s3-use-deep-archive or --s3-use-glacier) it fails: Last full backup date: Wed Apr 29 17:45:32 2020 RESTART: Volumes 2 to 2 failed to upload before termination. Restarting backup at volume 2. Attempt 1 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class Attempt 2 failed. ClientError: An error occurred (InvalidObjectState) when calling the GetObject operation: The operation is not valid for the object's storage class This is because a file stored in glacier cannot be downloaded. I dont know if this known? To solve this: either skip validate_encryption_settings() when using any of this storage backends or introduce an option to skip the download manually (e.g. --skip-download-on-restart) I fixed it for me with manully skipping the validate_encryption_settings() function. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1875937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876446] Re: WebDAV backend creates only tiny or 0 Byte files
** Also affects: duplicity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1876446 Title: WebDAV backend creates only tiny or 0 Byte files Status in Duplicity: In Progress Status in duplicity package in Ubuntu: Triaged Bug description: When using the WebDAV backend only tiny or 0-Byte files get created at the WebDAV storage. Duplicity itself doesn't report any error, only the uploaded file size is too small. Duplicity version: 0.8.12.1596 Python version: 3.6.10 OS Distro and version: gentoo Type of target filesystem: Linux, Windows, other.: WebDAV I created a 1000 Byte testfile. The uploaded file sizes are way too small: ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T104649Z.vol1.difftar.gpg ... WebDAV data length: 78 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full-signatures.20200502T104649Z.sigtar.gpg ... WebDAV data length: 138 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T104649Z.manifest.gpg ... WebDAV data length: 129 WebDAV response status 201 with reason 'Created'. ... Verification of this backup fails. I made a small fix in duplicity/backends/webdavbackend.py (see attachment) Now everything works as expected: ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T105219Z.vol1.difftar.gpg ... WebDAV data length: 28794233 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full-signatures.20200502T105219Z.sigtar.gpg ... WebDAV data length: 169724 WebDAV response status 201 with reason 'Created'. ... WebDAV PUT /remote.php/dav/files/myPath/test/duplicity-full.20200502T105219Z.manifest.gpg ... WebDAV data length: 1332 WebDAV response status 201 with reason 'Created'. ... Verification of this backup was successful. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1876446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876778] Re: MEGA.nz backend issues after "conversion" to Python 3 (patch attached)
** Also affects: duplicity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1876778
Title:
MEGA.nz backend issues after "conversion" to Python 3 (patch attached)
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
New
Bug description:
Hello, despite I have never written anything in Python, it looks like
the problem is some automatic code "conversion" to make this
"duplicity" backend work with Python 3, or a similar issue, if the
fundamental issue is another please ignore and stick to the facts
below, thank you.
After upgrading from Ubuntu 18.04 LTS to 20.04 LTS, my "duplicity"-based
backup to offsite MEGA.nz stopped working. This is what I was getting as a
result (output shown for a fresh new test backup):
"""
export BACKUP_SOURCE="/tmp"
export BACKUP_DESTINATION="mega://mega_usern...@example.com@mega.co.nz/Test_2"
# duplicity --full-if-older-than 30D ${BACKUP_SOURCE} ${BACKUP_DESTINATION}
mkdir: Test_2
megals: /Root/Test_2
Attempt 1 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 2 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 3 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 4 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Giving up after 5 attempts. TypeError: a bytes-like object is required, not
'str'
mkdir: Test_2
megals: /Root/Test_2
Attempt 1 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 2 failed. TypeError: a bytes-like object is required, not 'str'
megals: /Root/Test_2
Attempt 3 failed. TypeError: a bytes-like object is required, not 'str'
"""
After some research found out some calls to Python were being given a
byte-like object instead of strings (str). So googled around and added
some ".decode()" calls at some points in which strings were expected
(some trial and error seeing all similar errors in the MEGA.nz backend
data flow. After doing so, the backend resumed working normally
(resulting patch against current "duplicity" package is attached). So
please make a good patch from the one attached as reference and please
make its way into the Ubuntu package ASAP (don't know if upstream
version is affected as well).
More details about my current system:
"""
# lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04
# apt-cache policy duplicity
duplicity:
Instalados: 0.8.11.1612-1
Candidato: 0.8.11.1612-1
Tabla de versión:
*** 0.8.11.1612-1 500
500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
"""
Hope you find this valuable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1876778/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871757] Re: Duplicity fails backups at the end every time
** Also affects: duplicity Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1871757 Title: Duplicity fails backups at the end every time Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Backup seems to progress well (it takes a long time) and ends up with this error: Traceback (innermost last): File "/usr/bin/duplicity", line 1555, in with_tempdir(main) File "/usr/bin/duplicity", line 1541, in with_tempdir fn() File "/usr/bin/duplicity", line 1393, in main do_backup(action) File "/usr/bin/duplicity", line 1472, in do_backup restore(col_stats) File "/usr/bin/duplicity", line 728, in restore restore_get_patched_rop_iter(col_stats)): File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in Write_ROPaths for ropath in rop_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in integrate_patch_iters for patch_seq in collated: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in yield_tuples setrorps(overflow, elems) File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in setrorps elems[i] = iter_list[i].next() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in filter_path_iter for path in path_iter: File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in difftar2path_iter tarinfo_list = [tar_iter.next()] File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in next self.set_tarfile() File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in set_tarfile self.current_fp = self.fileobj_iter.next() File "/usr/bin/duplicity", line 764, in get_fileobj_iter backup_set.volume_name_dict[vol_num], KeyError: 8 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-11 (849 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: duplicity 0.7.17-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-05 (673 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1871757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871763] Re: Duplicity is not working
** Also affects: duplicity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1871763 Title: Duplicity is not working Status in Duplicity: New Status in duplicity package in Ubuntu: New Bug description: Duplicity is failing to make backup. It produces error message: see attached 000_Error_message.png After starting duplicity from terminal, I got much better error message: unim95@ubuntu-BitFenix-Prodigy:~$ duplicity bash: /usr/bin/duplicity: /usr/bin/python2: bad interpreter: No such file or directory After searching system for python2 i found, that there is no python2 executable unim95@ubuntu-BitFenix-Prodigy:~$ locate python2 | grep -v lib | grep -v man | grep -v doc | grep -v include /etc/python2.7 /etc/python2.7/sitecustomize.py /snap/core/8689/usr/share/bash-completion/completions/python2 /snap/core/8689/usr/share/dh-python/dh_python2 /snap/core/8689/usr/share/dh-python/dist/cpython2_fallback /snap/core/8935/usr/share/bash-completion/completions/python2 /snap/core/8935/usr/share/dh-python/dh_python2 /snap/core/8935/usr/share/dh-python/dist/cpython2_fallback /usr/bin/python2-futurize /usr/bin/python2-pasteurize /usr/bin/python2.7 /usr/bin/python2.7-config /usr/bin/waitress-serve-python2 /usr/bin/x86_64-linux-gnu-python2.7-config /usr/share/app-install/desktop/idle-python2.7:idle-python2.7.desktop /usr/share/applications/python2.7.desktop /usr/share/bash-completion/completions/python2 /usr/share/binfmts/python2.7 /usr/share/dh-python/dh_python2 /usr/share/dh-python/dist/cpython2_fallback /usr/share/lintian/overrides/python2.7 /usr/share/lintian/overrides/python2.7-minimal /usr/share/pixmaps/python2.7.xpm Default python is: unim95@ubuntu-BitFenix-Prodigy:~$ python --version Python 2.7.17 Duplicity version: unim95@ubuntu-BitFenix-Prodigy:~$ dpkg -s duplicity Package: duplicity Status: install ok installed Priority: optional Section: utils Installed-Size: 1064 Maintainer: Ubuntu Developers Architecture: amd64 Version: 0.7.17-0ubuntu1.1 Depends: libc6 (>= 2.4), librsync1 (>= 0.9.6), python (<< 2.8), python (>= 2.7~), python-fasteners, python:any (<< 2.8), python:any (>= 2.7.5-5~), python-lockfile (>> 1:0.9), gnupg | gnupg1 Suggests: rsync, python-paramiko, python-pexpect, python-urllib3, python-oauthlib, python-boto, ncftp, python-cloudfiles, lftp, python-gdata, tahoe-lafs, python-swiftclient Description: encrypted bandwidth-efficient backup Duplicity backs directories by producing encrypted tar-format volumes and uploading them to a remote or local file server. Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Because duplicity uses GnuPG to encrypt and/or sign these archives, they will be safe from spying and/or modification by the server. Homepage: http://duplicity.nongnu.org/ Original-Maintainer: Alexander Zangerl Python2 version: unim95@ubuntu-BitFenix-Prodigy:~$ dpkg -s python Package: python Status: install ok installed Priority: optional Section: python Installed-Size: 624 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: allowed Source: python-defaults Version: 2.7.15~rc1-1 Replaces: python-dev (<< 2.6.5-2) Provides: python-ctypes, python-email, python-importlib, python-profiler, python-wsgiref Depends: python2.7 (>= 2.7.15~rc1-1~), libpython-stdlib (= 2.7.15~rc1-1) Pre-Depends: python-minimal (= 2.7.15~rc1-1) Suggests: python-doc (= 2.7.15~rc1-1), python-tk (>= 2.7.15~rc1-1~) Breaks: update-manager-core (<< 0.200.5-2) Conflicts: python-central (<< 0.5.5) Description: interactive high-level object-oriented language (default version) Python, the high-level, interactive object oriented language, includes an extensive class library with lots of goodies for network programming, system administration, sounds and graphics. . This package is a dependency package, which depends on Debian's default Python version (currently v2.7). Original-Maintainer: Matthias Klose Homepage: http://www.python.org/ Cnf-Extra-Commands: python Cnf-Priority-Bonus: 3 OS: unim95@ubuntu-BitFenix-Prodigy:~$ cat /etc/os-release NAME="Ubuntu" VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic FS used: ext4. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/187
[Desktop-packages] [Bug 1407966] Re: S3: Unable to access european buckets, new authorization mechanism not supported AWS4-HMAC-SHA256
Then get the repo managers to change their policy. duplicity is up to 0.8.12 now, but it's not even in the repo to go out with Ubuntu 20.04. Other packages like boto are in the same shape. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1407966 Title: S3: Unable to access european buckets, new authorization mechanism not supported AWS4-HMAC-SHA256 Status in Duplicity: Invalid Status in duplicity package in Ubuntu: New Status in Debian: New Bug description: Accessing a bucket that was created in the AWS console in the German location Frankfurt is not working, due to Amazon requiring some new authentication method. I made a minor modification to the code as outlined in bug #1278529 to have the exception raised instead of displaying "No connection to backend". To reproduce create a bucket in the Frankfurt location and try to access it using duplicity. duplicity full -v9 --s3-european-buckets --s3-use-new-style /path/to/backup s3+http://my-european-bucket/my-backup-path Exit code: 30 Using archive dir: /home/dave/.cache/duplicity/251e8f41ea8795b16a9fc8f0be2d4fa2 Using backup name: 251e8f41ea8795b16a9fc8f0be2d4fa2 Import of duplicity.backends.botobackend Succeeded Import of duplicity.backends.cfbackend Succeeded Import of duplicity.backends.dpbxbackend Succeeded Import of duplicity.backends.ftpbackend Succeeded Import of duplicity.backends.ftpsbackend Succeeded Import of duplicity.backends.gdocsbackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.megabackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.sshbackend Succeeded Import of duplicity.backends.swiftbackend Succeeded Import of duplicity.backends.tahoebackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Import of duplicity.backends.~par2wrapperbackend Succeeded Using temporary directory /tmp/duplicity-uPZnQI-tempdir Traceback (most recent call last): File "/usr/bin/duplicity", line 1509, in with_tempdir(main) File "/usr/bin/duplicity", line 1503, in with_tempdir fn() File "/usr/bin/duplicity", line 1336, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 1059, in ProcessCommandLine backup, local_pathname = set_backend(args[0], args[1]) File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 952, in set_backend globals.backend = backend.get_backend(bend) File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 163, in get_backend return _backends[pu.scheme](pu) File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", line 163, in __init__ self.resetConnection() File "/usr/lib/python2.7/dist-packages/duplicity/backends/_boto_single.py", line 186, in resetConnection self.bucket = self.conn.lookup(self.bucket_name) File "/usr/lib/python2.7/dist-packages/boto/s3/connection.py", line 376, in lookup bucket = self.get_bucket(bucket_name, validate, headers=headers) File "/usr/lib/python2.7/dist-packages/boto/s3/connection.py", line 371, in get_bucket bucket.get_all_keys(headers, maxkeys=0) File "/usr/lib/python2.7/dist-packages/boto/s3/bucket.py", line 347, in get_all_keys '', headers, **params) File "/usr/lib/python2.7/dist-packages/boto/s3/bucket.py", line 314, in _get_all response.status, response.reason, body) S3ResponseError: S3ResponseError: 400 Bad Request InvalidRequestThe authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.E3E4915B08D90EA6tkxe/V3CcQ6fnyLsvXDp3uABC1ppfBpvmZkA17wyGyIOjhhjyylTNhxm+5jGNRDY4SWLCQH+brg= To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1407966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867529] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0: ordinal not in range(128) with PCA
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1867529
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position
0: ordinal not in range(128) with PCA
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
New
Bug description:
Same kind of bug after last fix :
I am using duplicity 0.8.11.1607 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200315T171233Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(util.fsdecode(source_path.name)))
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
422, in _request
return self.request_session.request(*arg, **kwarg)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py", line
520, in request
resp = self.send(prep, **send_kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py", line
630, in send
r = adapter.send(request, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/adapters.py", line
460, in send
for i in request.body:
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/utils.py", line
279, in __next__
chunk = self.content.read(self.chunk_size)
File "/snap/duplicity/86/usr/lib/python3.6/encodings/ascii.py", line 26, in
decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0:
ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1867529/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867444] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0: ordinal not in range(128) using PCA backend
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1867444
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position
0: ordinal not in range(128) using PCA backend
Status in Duplicity:
Fix Released
Status in duplicity package in Ubuntu:
New
Bug description:
Sorry but after last fix, I have another error.
I am using duplicity 0.8.11.1606 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200314T160021Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(source_path.name))
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
422, in _request
return self.request_session.request(*arg, **kwarg)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/requests/sessions.py", line
520, in request
resp = self.send(prep, **send_kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/requests/sessions.py", line
630, in send
r = adapter.send(request, **kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/requests/adapters.py", line
460, in send
for i in request.body:
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/utils.py", line
279, in __next__
chunk = self.content.read(self.chunk_size)
File "/snap/duplicity/84/usr/lib/python3.6/encodings/ascii.py", line 26, in
decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0:
ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1867444/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867435] Re: TypeError: must be str, not bytes using PCA backend
** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1867435 Title: TypeError: must be str, not bytes using PCA backend Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: New Bug description: I am using duplicity 0.8.11.1604 from snap edge channel. I am trying to use multi backend with one of them being the OVH PCA. It fails when trying to write to the PCA with the following error : MultiBackend: _put: write to store #0 (pca://backupPortableX-cold) Writing cold_duplicity-full.20200314T135032Z.vol1.difftar.gpg Backtrace of previous error: Traceback (innermost last): File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 376, in inner_retry return fn(self, *args) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 547, in put self.__do_put(source_path, remote_filename) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 533, in __do_put self.backend._put(source_path, remote_filename) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backends/pcabackend.py", line 153, in _put self.conn.put_object(self.container, self.prefix + remote_filename, TypeError: must be str, not bytes To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1867435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867742] Re: TypeError: fsdecode() takes 1 positional argument but 2 were given with PCA backend
** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1867742 Title: TypeError: fsdecode() takes 1 positional argument but 2 were given with PCA backend Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: New Bug description: I am using 0.8.11-0ubuntu1ppa1609~ubuntu18.04.1 package and trying to use PCA backend. Here is the error : MultiBackend: _put: write to store #0 (pca://backupPortableX-cold) Writing cold_duplicity-full.20200317T082259Z.vol1.difftar.gpg Backtrace of previous error: Traceback (innermost last): File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 376, in inner_retry return fn(self, *args) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 547, in put self.__do_put(source_path, remote_filename) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 533, in __do_put self.backend._put(source_path, remote_filename) File "/usr/lib/python3/dist-packages/duplicity/backends/pcabackend.py", line 154, in _put open(util.fsdecode(source_path.name, u'rb'))) TypeError: fsdecode() takes 1 positional argument but 2 were given To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1867742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867742] Re: TypeError: fsdecode() takes 1 positional argument but 2 were given with PCA backend
Thanks for being persistent! ** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Importance: Undecided => Medium ** Changed in: duplicity Status: New => Fix Committed ** Changed in: duplicity Milestone: None => 0.8.12 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1867742 Title: TypeError: fsdecode() takes 1 positional argument but 2 were given with PCA backend Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: New Bug description: I am using 0.8.11-0ubuntu1ppa1609~ubuntu18.04.1 package and trying to use PCA backend. Here is the error : MultiBackend: _put: write to store #0 (pca://backupPortableX-cold) Writing cold_duplicity-full.20200317T082259Z.vol1.difftar.gpg Backtrace of previous error: Traceback (innermost last): File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 376, in inner_retry return fn(self, *args) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 547, in put self.__do_put(source_path, remote_filename) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 533, in __do_put self.backend._put(source_path, remote_filename) File "/usr/lib/python3/dist-packages/duplicity/backends/pcabackend.py", line 154, in _put open(util.fsdecode(source_path.name, u'rb'))) TypeError: fsdecode() takes 1 positional argument but 2 were given To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1867742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867529] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0: ordinal not in range(128) with PCA
** Changed in: duplicity
Status: In Progress => Fix Committed
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1867529
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position
0: ordinal not in range(128) with PCA
Status in Duplicity:
Fix Committed
Status in duplicity package in Ubuntu:
New
Bug description:
Same kind of bug after last fix :
I am using duplicity 0.8.11.1607 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200315T171233Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/86/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(util.fsdecode(source_path.name)))
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/client.py", line
422, in _request
return self.request_session.request(*arg, **kwarg)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py", line
520, in request
resp = self.send(prep, **send_kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/sessions.py", line
630, in send
r = adapter.send(request, **kwargs)
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/requests/adapters.py", line
460, in send
for i in request.body:
File
"/snap/duplicity/86/usr/lib/python3/dist-packages/swiftclient/utils.py", line
279, in __next__
chunk = self.content.read(self.chunk_size)
File "/snap/duplicity/86/usr/lib/python3.6/encodings/ascii.py", line 26, in
decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0:
ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1867529/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
