Package: s3ql Version: 3.7.0+dfsg-2 Followup-For: Bug #982381 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
A workaround, at least if (like me) you've got S3QL running as a dedicated user: As the s3ql-user, run: pip3 install --user trio==0.18.0 This will install a newer version of trio (0.18.0) in ~/.local/lib — once this bug is fixed, you can remove it. - -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (130, 'unstable-debug'), (130, 'unstable'), (120, 'experimental-debug'), (120, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages s3ql depends on: ii fuse3 [fuse] 3.10.3-1 ii libc6 2.31-12 ii libjs-sphinxdoc 3.4.3-2 ii libsqlite3-0 3.34.1-3 ii procps 2:3.3.17-5 ii psmisc 23.4-2 ii python3 3.9.2-3 ii python3-apsw 3.34.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-3 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. - -- no debconf information -----BEGIN PGP SIGNATURE----- iHMEARECADMWIQTlAc7j4DAtSNRJJ0z7P4jCVepZ/gUCYLmngRUcYW50aG9ueUBk ZXJvYmVydC5uZXQACgkQ+z+IwlXqWf6kkwCfckQ/FVPZa3RBFNBC3PR6PJrfmUUA n3d/GbFiwu8Spi1gwUrh0DKZmxth =ZUtK -----END PGP SIGNATURE-----
