Just to complete the story so far. SSH appears to be set up correctly. I get this:
C:\Development\Wireshark>ssh -p 29418 USERNAME@xxxxxxxxxxxxxxxxxx
Enter passphrase for key '/home/my_userid/.ssh/id_rsa':
**** Welcome to Gerrit Code Review ****
Hi Paul Offord, you have successfully connected over SSH.
Unfortunately, interactive shells are disabled.
To clone a hosted Git repository, use:
git clone ssh://USERNAME@xxxxxxxxxxxxxxxxxx:29418/REPOSITORY_NAME.git
Connection to code.wireshark.org closed.
If I then try git review I get this:
C:\Development\Wireshark>git review
Problem running 'git remote update origin'
Fetching origin
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
error: Could not fetch origin
There definitely seems to be a problem with the linkage between git and SSH.
Best regards…Paul
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx]
On Behalf Of Paul Offord
Sent: 30 November 2015 08:32
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Setting up git for gerrit
Hi Graham,
That may explain why I am having a frustrating time with this. I’ve spent about 6 hours so far trying to push a fix to gerrit – I
had all but given up. In answer to your questions:
·
git --version is git version 2.6.2.windows.1
·
git-review --version is git-review version 1.25.0
·
where.exe ssh.exe gives C:\cygwin64\bin\ssh.exe
·
python --version give Python 2.7.10
Best regards…Paul
From:
wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx]
On Behalf Of Graham Bloice
Sent: 30 November 2015 07:40
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Setting up git for gerrit
On 29 November 2015 at 23:19, Paul Offord <Paul.Offord@xxxxxxxxxxxx> wrote:
Hi,
I’m trying to setup git so that I can submit a change to gerrit. Although I can use git pull to update the code, when I try git review I get:
C:\Development\Wireshark>git review
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'https://code.wireshark.org': Invalid argument
I’m pretty sure this is an authentication issue. I’ve set my SSH public key in gerrit and an HTTPS password. Details of the access are:
C:\Development\Wireshark>git remote -v
origin
https://code.wireshark.org/review/wireshark (fetch)
origin
https://code.wireshark.org/review/wireshark (push)
What should git remote –v look like if I have things setup correctly?
Thanks and regards…Paul
Note that the latest git for Windows causes some issues with git review, depending on how you install it.
So firstly your environment, what is your git version (git --version), git-review version (git-review --version) and do you have ssh.exe from path\to\git\usr\bin on the path (where.exe ssh.exe)?
Are you running a Windows native python, what version of python?
______________________________________________________________________
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
Any views or opinions expressed are solely those of the author and do not necessarily represent those of Advance Seven Ltd. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.
Advance Seven Ltd. Registered in England & Wales numbered 2373877 at Endeavour House, Coopers End Lane, Stansted, Essex CM24 1SJ
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
