Bug#1071675: duplicity: SSH broken with Paramiko 3.4

2024-05-27 Thread Alexander Zangerl
reassign 1071675 python3-paramiko 3.4.0-1 retitle 1071675 "paramiko: ed25519 broken" tags 1071675 -moreinfo -unreproducible +upstream thanks On Mon, 27 May 2024 10:16:38 -0700, tony mancill writes: >It's happening here too, for backups using an ed25519 SSH key that has >worked with duplicity in th

Bug#1071675: duplicity: SSH broken with Paramiko 3.4

2024-05-27 Thread tony mancill
On Fri, May 24, 2024 at 09:05:17AM +1000, Alexander Zangerl wrote: > tags 1071675 +moreinfo +unreproducible > severity 1071675 normal > thanks > > On Thu, 23 May 2024 18:16:58 +0200, Fiona Klute writes: > >When trying to do backup to an sftp:// target Duplicity fails since > >python3-paramiko was

Bug#1071675: duplicity: SSH broken with Paramiko 3.4

2024-05-23 Thread Alexander Zangerl
tags 1071675 +moreinfo +unreproducible severity 1071675 normal thanks On Thu, 23 May 2024 18:16:58 +0200, Fiona Klute writes: >When trying to do backup to an sftp:// target Duplicity fails since >python3-paramiko was updated to 3.4.0-1, with the following error which >looks like an API change in P

Bug#1071675: duplicity: SSH broken with Paramiko 3.4

2024-05-23 Thread Fiona Klute
Package: duplicity Version: 2.1.4-3+b1 Severity: important When trying to do backup to an sftp:// target Duplicity fails since python3-paramiko was updated to 3.4.0-1, with the following error which looks like an API change in Paramiko: ssh: Unknown exception: public_blob ssh: Traceback (most re