Your message dated Wed, 8 Oct 2014 10:30:13 -0400 with message-id <canyoob1hcymw8mxiu5cswosp4g9hequkb1whjsdjw4gzsme...@mail.gmail.com> and subject line request to close 682241 has caused the Debian Bug report #682241, regarding bzr launchpad plugin fails if ssh-agent has other than launchpad key first to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 682241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682241 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: bzr Version: 2.6.0~bzr6526-1 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Dear Maintainer, I used bzr to branch a project from launchpad. It worked, but gave me a warning that I should set up my launchpad userid. I set my launchpad id, then tried to do a bzr branch with an lp: url bzr branch lp:openshot I started getting bzr errors: ssh_exchange_identification: read: Connection reset by peer ConnectionReset reading response for 'BzrDir.open_2.1', retrying ssh_exchange_identification: read: Connection reset by peer bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist. I added my launchpad.net ssh public key (note that I already had some keys in my ssh-agent) with ssh-add. I still got the bzr error. I deleted all the keys from my ssh-agent. I then added my launchpad key to the agent. I was then able to do the bzr branch. I then added other ssh keys and was still able to do the branch. thanks, Brian Minton - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.4.3 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages bzr depends on: ii python 2.7.3-1 ii python-bzrlib 2.6.0~bzr6526-1 Versions of packages bzr recommends: ii python-gpgme 0.2-2 Versions of packages bzr suggests: ii bzr-doc 2.6.0~bzr6526-1 ii bzr-gtk 0.103.0+bzr792-3 ii bzr-svn 1.2.1-1 ii bzrtools 2.5+bzr786-2 ii python-bzrlib.tests 2.6.0~bzr6526-1 - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEAREDAAYFAlAJgCoACgkQ2/alund99IegQACgqMMAAgjpeZNixYO/ki66phnx 4BwAnii+5Qp421iVpeg0nIIEjml5eYEz =rzQn -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 I'm requesting to close this bug because it was caused by user error on my part. regards, Brian Minton -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEAREDAAYFAlQ1SlkACgkQ2/alund99IdRDwCfRQUxF9C3wMAtnceh5VyMDit9 xgwAoJDkfNBNihbMQfmQwb9wasm9p86W =zHNA -----END PGP SIGNATURE-----
--- End Message ---
