<div dir="ltr"><div class="gmail_quote"><div class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr"><br></div><div dir="ltr" class="gmail_attr">On Thu, Jun 9, 2022 at 4:20 PM Maarten Hoes <<a href="mailto:hoes.maarten@gmail.com">hoes.maarten@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br>What I think I see happening is that the client is trying to force 'sftp' when the scp command is used, and the server is not having it ? Or perhaps I am simply using the wrong command to clone the repo and set it up for commiting / putting things up for review ? <br><br></div></blockquote><div><br></div><div>
<div>Hrm.</div><div><br></div><div>I did some more googling, and came across scp's '-O' switch, which as described in the man page :</div><div><br></div><div>"</div><div>-O
Use the original SCP protocol for file transfers instead of the
SFTP protocol. Forcing the use of the SCP protocol may be necessary for
servers that do not implement SFTP, for backwards-compatibility for
particular filename wildcard patterns and for expanding paths with a ‘~’
prefix for older<br> SFTP servers.</div><div>"</div><div><br></div><div><br></div><div>And if I add that to the scp commandline, it all works as expected, and I was able to put my changes up for review in gerrit, doing the following, as I mentioned in my earlier email :<br></div></div><div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">cd buildbot/lcov-report/<br>git checkout -b lcov-report<br>cp ~/bin/libreoffice/README ~/bin/libreoffice/lcov-report.sh .<br>git add README lcov-report.sh<br>git commit<br>git push origin lcov-report:refs/for/master</div></blockquote><div><br></div><div><br></div><div>But perhaps someone should look at this for a more structural solution ? <br></div><div><br></div><div><br></div><div>- Maarten<br></div></div></div>