EasyBreezy

First-time use of new repo

Bug #1835082 reported by Robert Ladyman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EasyBreezy
Status tracked in Trunk
Trunk
Fix Released
High
Robert Ladyman

Bug Description

The first time you use 'bzr GET existing project' against a new repository, you might get an empty list, even with the correct name and password - this is probably because you have yet to accept the ECDSA fingerprint (the prompt you get from ssh the first time you try to connect).

FAQ added to give a work-around, but we should really detect this with sshpass (or use something like:

ssh-copy-id -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null...)

Tags: ui
Revision history for this message
Robert Ladyman (saccadic-masking) wrote :

This has just bitten me - for a non-technical user, this is a show-stopper.

Revision history for this message
Robert Ladyman (saccadic-masking) wrote :

Added -o StrictHostKeyChecking=no to runcheckout.sh and runnewproject.sh

** Warning ** this means that a user will automatically connect and ignore any key warnings on first connect.

Changed in easybreezy:
assignee: nobody → Robert Ladyman (saccadic-masking)
status: New → In Progress
importance: Undecided → High
Robert Ladyman (saccadic-masking)
tags: added: ui
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.