Package: s3ql Version: 3.7.0+dfsg-2 Followup-For: Bug #983170 Now that bullseye has shipped, and I have moved on to bookworm, I am keen to do anything I can to help resolve this. Is there anything I can do? For example testing with packages? Or is there an upstream fix available for testing?
-- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_IE.utf8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages s3ql depends on: ii fuse3 [fuse] 3.10.4-1 ii libc6 2.31-17 ii libjs-sphinxdoc 3.5.4-2 ii libsqlite3-0 3.36.0-2 ii procps 2:3.3.17-5 ii psmisc 23.4-2 ii python3 3.9.2-3 ii python3-apsw 3.36.0-r1-1 ii python3-cryptography 3.3.2-1 ii python3-defusedxml 0.6.0-2 ii python3-dugong 3.8.1+dfsg-1 ii python3-google-auth 1.5.1-3 ii python3-google-auth-oauthlib 0.4.2-1 ii python3-pkg-resources 52.0.0-4 ii python3-pyfuse3 3.2.0-2 ii python3-requests 2.25.1+dfsg-2 ii python3-systemd 234-3+b4 ii python3-trio 0.13.0-2 s3ql recommends no packages. s3ql suggests no packages. -- debconf-show failed
