Sean 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 ?
Is it possible that dput is being influenced by things in the package
directory ? I notice that dgit is saying `../cmake.changes` and your
quoted working command is `foo_source.changes` from which I might
infer that your successful command is being run in a different
directory.
dgit will show its chdirs if you say -D, but I believe that it runs
the dput from the package working tree.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
