TypeError: cannot use a string pattern on a bytes-like object

Bug #1908971 reported by Sod Oscarfono
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Undecided
Unassigned
duplicity (Ubuntu)
New
Undecided
Unassigned

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=<set>
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Sod Oscarfono (sod) wrote :
Changed in duplicity:
status: New → Incomplete
Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote :

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.

Revision history for this message
Sod Oscarfono (sod) wrote :

resolved by upgrading to version 0.8.17

thanks Kenneth.

Changed in duplicity:
status: Incomplete → Fix Released
Revision history for this message
Jon Yoon (jony-labkey) wrote :

I ran into the same issue, but upgrading to 0.8.19 didn't fix it.

I've put in a new bug for this: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1930640

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.