why I can't get the update of dhis2 trunk now?

Support - Assistance technique
#1

I can got by bzr pull or bzr update,but now:

Unable to negotiate with 91.189.95.84: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1
ConnectionReset reading response for ‘BzrDir.open_2.1’, retrying
Unable to negotiate with 91.189.95.84: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1
bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.

I have run the pageant with key.

···

–
此致

林晓东

莫愁前路无知己，天下谁人不识君。

#2

This likely related to following and you may have to change your openssh options.
http://www.openssh.com/legacy.html

The server offered only a single method diffie-hellman-group1-sha1. OpenSSH supports this method, but does not enable it by default because is weak and within theoretical range of the so-called Logjam attack.

Dan Cocos
Principal, BAO Systems

+1 202-352-2671 | dcocos@baosystems.com | http://www.baosystems.com | Skype: dancocos | 2900 K Street, Suite 404, Washington D.C. 20007

···

On Oct 13, 2015, at 5:42 AM, 林晓东 lin_xd@126.com wrote:

I can got by bzr pull or bzr update,but now:

Unable to negotiate with 91.189.95.84: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1
ConnectionReset reading response for ‘BzrDir.open_2.1’, retrying
Unable to negotiate with 91.189.95.84: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1
bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.

I have run the pageant with key.

–
此致

林晓东

莫愁前路无知己，天下谁人不识君。

Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp