Package: deja-dup Version: 36.2-1 Severity: important Dear Maintainer,
deja-dup fails with a MemoryError in `duplicity/manifest.py` when creating or resuming a backup. Cleaning `.cache/deja-dup` seems to be a workaround. But in the next backup, it will fail again. Will provide more information if needed. Maybe related to a large manifest file (102M)? -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages deja-dup depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.1-1 ii duplicity 0.7.14-2 ii libatk1.0-0 2.26.1-1 ii libc6 2.24-17 ii libglib2.0-0 2.54.2-1 ii libgoa-1.0-0b 3.26.1-1 ii libgoa-backend-1.0-1 3.26.1-1 ii libgtk-3-0 3.22.25-1 ii libnautilus-extension1a 3.26.0-1 ii libpackagekit-glib2-18 1.1.7-1 ii libpango-1.0-0 1.40.13-1 ii libpeas-1.0-0 1.22.0-1+b1 ii libsecret-1-0 0.18.5-4 Versions of packages deja-dup recommends: ii gvfs-backends 1.34.1-1 ii packagekit 1.1.7-1 ii policykit-1 0.105-18 Versions of packages deja-dup suggests: ii python-boto 2.44.0-1 ii python-cloudfiles 1.7.11-3 pn python-swiftclient <none> -- no debconf information