[Q-e-developers] new portal and ssh key
Filippo Spiga
spiga.filippo at gmail.com
Tue Aug 21 02:12:27 CEST 2012
Ciao Lorenzo,
I also had to remove duplicates (there were duplicates? weird…) inside ~/.ssh/known_hosts
Moreover, I did not check-out from scratch QE but I managed to "convert" my working copy to work with the new repository address. I used a script provided by Erica plus one line change… if this is your case (adapt a working copy), Erica can help!
Cheers,
Filippo
On Aug 20, 2012, at 9:31 PM, Lorenzo Paulatto <Lorenzo.Paulatto at impmc.upmc.fr> wrote:
> I'm writing you as I just lost half an hour running after this..
>
> If you are trying to use the svn access to some qe-forge prohect, and you get this kind of messages:
> svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
> svn: Network connection closed unexpectedly
>
> It is because with the new qe-forge portal also came a new ssh key. In order to make it work again you have to clean up the ~/.ssh/known_hosts file, removing the line pertaining to scm.qe-forge.org. Also the command
> ssh-keygen -R scm.qe-forge.org
> should work, but I did not try it personally.
>
> bests
--
Mr. Filippo SPIGA, M.Sc., Ph.D. Candidate
CADMOS - Chair of Numerical Algorithms and HPC (ANCHP)
École Polytechnique Fédérale de Lausanne (EPFL)
http://anchp.epfl.ch ~ http://filippospiga.me ~ skype: filippo.spiga
«Nobody will drive us out of Cantor's paradise.» ~ David Hilbert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quantum-espresso.org/pipermail/developers/attachments/20120821/6e6228a6/attachment.html>
More information about the developers
mailing list