Control: reassign -1 python3-paramiko Hi Ian and Sean,
* Ian Jackson <[email protected]> [2025-02-16 11:57]:
It happens repeatedly. I ran dput with the same changes files, but from the parent directory where it resides. I just tried to reproduce it with a different package, and now it fails consistently with "dput ssh-upload" as well, so I'm afraid I may have messed up in the diagnosis and mistakenly ran dput without ssh-upload, so itSean Whitton writes ("Bug#1096078: dgit: paramiko exception during upload with @cert-authority in /etc/ssh/ssh_known_hosts"):On Sat 15 Feb 2025 at 09:45pm +01, Timo Röhling wrote:...> the "dgit push-source" command no longer works since I put an SSH > certificate authority in my /etc/ssh/known_hosts file. I've also set > "dgit-distro.debian.upload-host" to "ssh-upload" (which is the > default SFTP profile of dput). > > Interestingly, invoking "dput ssh-upload foo_source.changes" > directly works just fine, which is why I assume that this must be > somehow related to the way dgit invokes dput. Very strange. dgit simply does 'dput ssh-upload ../cmake_3.31.5-2~bpo12+1_source.changes' and nothing fancier.Weird, indeed. You can see the complete and precise dput command that dgit is running in the error output in your initial report: dgit: failed command: dput ssh-upload '../cmake_3.31.5-2~bpo12+1_source.changes' It's also shown before it's run if you pass dgit the -D option. I hate to ask this, but: is this a thing that happened once, or does it happen repeatably ?
uploaded via FTP and avoided the SSH issue.Sorry for the noise, reassigning to python3-paramiko for further analysis.
Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀ ╭────────────────────────────────────────────────────╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄⠀⠀⠀⠀ ╰────────────────────────────────────────────────────╯
signature.asc
Description: PGP signature

