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?
--
Package: s3ql
Version: 3.7.0+dfsg-2
Followup-For: Bug #983170
The mount.log consists of minor variations on the following...
2021-02-20 13:21:46.208 238604:MainThread s3ql.mount.determine_threads: Using
10 upload threads.
2021-02-20 13:21:46.210 238604:MainThread s3ql.mount.main: Autodetected
On Sat, Feb 20, 2021 at 01:24:16PM +, Graham Cobb wrote:
Package: s3ql
Version: 3.7.0+dfsg-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that
severity 983170 grave
tags 983170 + upstream help
thanks
It seems to me that this version cannot simply be distributed as is.
Even, the wrong assumption about trio version compatibility renders it not
compatible with bullseye status.
On Sat, Feb 20, 2021 at 01:24:16PM +, Graham Cobb
Package: s3ql
Version: 3.7.0+dfsg-2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome
5 matches
Mail list logo
